problem running MS SQL Web Data Admin

Hi:
My client machine is XP Pro with SP1 with IIS 5.1 My server machine is
Windows 2000 server SP4 with IIS 5.0. Server has the latest MSDE 2000(SP3a,
in mixed mode) as well as MS SQL Web Data Admin (webadmin) installed on it.
I can use webadmin on the server to access data in MSDE using windows auth
as well as SQL login.
I then installed webadmin on the Client machine but can't get it to connect
to the MSDE on the server machine. I looked at KB article: 319930 and
ensured that test.udl on client XP machine can connect fine using TCP/IP and
sa userid to the MSDE on the server machine. But webadmin won't connect.
Here's the error message:
Server Error in '/webadmin' Application.
COM object with CLSID {10020200-E260-11CF-AE68-00AA004A34D5} is either not
valid or not registered.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: COM object
with CLSID {10020200-E260-11CF-AE68-00AA004A34D5} is either not valid or not
registered.
Source Error:
An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.
Stack Trace:
[COMException (0x80040154): COM object with CLSID
{10020200-E260-11CF-AE68-00AA004A34D5} is either not valid or not
registered.]
SqlAdmin.SqlServer.Connect()
SqlWebAdmin.databases.Page_Load(Object sender, EventArgs e) +28
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +731
Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
Version:1.1.4322.573
Other ASP.NET starter kit apps (like Commerce and Portal) work fine from
Client machine using MSDE on the server. The problem seems to be with
webadmin. Any suggestions would be appreciated.
Vamsee Lakamsani
lakamsani AT gmail.com
The web data admin package needs a dll called SQLDMO.dll that is a com object that is only installed from the full version of SQL server, not with MSDE. That is the com object error message you are receiving.
"vl" wrote:

> Hi:
> My client machine is XP Pro with SP1 with IIS 5.1 My server machine is
> Windows 2000 server SP4 with IIS 5.0. Server has the latest MSDE 2000(SP3a,
> in mixed mode) as well as MS SQL Web Data Admin (webadmin) installed on it.
> I can use webadmin on the server to access data in MSDE using windows auth
> as well as SQL login.
> I then installed webadmin on the Client machine but can't get it to connect
> to the MSDE on the server machine. I looked at KB article: 319930 and
> ensured that test.udl on client XP machine can connect fine using TCP/IP and
> sa userid to the MSDE on the server machine. But webadmin won't connect.
> Here's the error message:
> --
> Server Error in '/webadmin' Application.
> ----
> --
> COM object with CLSID {10020200-E260-11CF-AE68-00AA004A34D5} is either not
> valid or not registered.
> Description: An unhandled exception occurred during the execution of the
> current web request. Please review the stack trace for more information
> about the error and where it originated in the code.
> Exception Details: System.Runtime.InteropServices.COMException: COM object
> with CLSID {10020200-E260-11CF-AE68-00AA004A34D5} is either not valid or not
> registered.
> Source Error:
> An unhandled exception was generated during the execution of the current web
> request. Information regarding the origin and location of the exception can
> be identified using the exception stack trace below.
> Stack Trace:
>
> [COMException (0x80040154): COM object with CLSID
> {10020200-E260-11CF-AE68-00AA004A34D5} is either not valid or not
> registered.]
> SqlAdmin.SqlServer.Connect()
> SqlWebAdmin.databases.Page_Load(Object sender, EventArgs e) +28
> System.Web.UI.Control.OnLoad(EventArgs e) +67
> System.Web.UI.Control.LoadRecursive() +35
> System.Web.UI.Page.ProcessRequestMain() +731
>
>
> ----
> --
> Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET
> Version:1.1.4322.573
> Other ASP.NET starter kit apps (like Commerce and Portal) work fine from
> Client machine using MSDE on the server. The problem seems to be with
> webadmin. Any suggestions would be appreciated.
> --
> Vamsee Lakamsani
> lakamsani AT gmail.com
>
>

Problem moving RS Virtual Directories

I installed RS using the default settings (but without SSL) and it worked fine. Then I installed SP1.
Initially installed to:
http://www.ourdomain.com/reports
http://www.ourdomain.com/reportserver
Then I attempted to move the virtual directories to take advantage of SSL and everything stopped.
So in IIS I created a new web site using a sub-domain:
http://reports.ourdomain.com and loaded a certificate.
Then I saved the 2 original virtual directories as config files and then re-installed them under this new web site e.g.
https://reports.ourdomain.com/reports
https://reports.ourdomain.com/reportserver
I then edited the config files RSWebApplication.config & RSReportServer.config with the following changes
<UrlRoot>http://OurServerName/ReportServer</UrlRoot> --> <UrlRoot>https://reports.ourdomain.com/ReportServer</UrlRoot>
<ReportServerUrl>http://OurServerName/ReportServer</ReportServerUrl> --> <ReportServerUrl>https://reports.ourdomain.com/ReportServer</ReportServerUrl>
And now nothing works... I get the "Server Error in '/REPORTS' Application." error i.e. an aspx error with nothing logged in the RS log.
Something I suspect is that changing the URL from the servername to the domain name is making the permissions act differently - but while its getting the aspx error I can't see what is going wrong. I can't even seem to make it give me the full error. Its giving me the standard:
"Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off"."
And even though the custom errors tag is set as specified its not giving me any error information.
Has anyone any suggestions as to what might be going wrong?

see if this article helps. there are a couple little weird thingsyou need for the virtual directories to work that you might not expect:
http://www.sqljunkies.com/Article/525B575A-7F61-483A-AC8F-FEC700C34674.scuk

Problem looping DTS and BCP within a Stored procedure

All,

This is the scenerio

SP=Stored Procedure

I call SP1 which calls a DTS package.

DTS package calls SP2 and SP2 calls SP3 and SP 4 using an IF condition

SP3 has 3 BCP OUT commands after which it calls SP1 again

Now, the problem is that if I follow all the steps, then only 1 of the BCP command executes and the control exits out of SP3 and returns control to SP1.

If I ignore SP1 and DTS and run SP2 independently, then all BCP steps in SP3 are executed and control returns to SP2

I ma not sure if using DTS and BCP in SQL stored procedures might cause any problems

Appreciate your helpIt seems like your DTS is executing under a different security context than when you execute your SP3 from QA. Are you checking for errors after each BCP in your SP3? If you're calling your BCP using xp_cmdshell, - consider doing INSERT @.temp_tbl exec master.dbo.xp_cmdshell [....].

Problem installing SQL Server 2005 Express with Advance Services CTP

Hi,

I was unable to install the CTP version of SS Express Edition SP1 with Advance Services. The installation failed with the following error message:

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

However, I was able to install and run the standard CTP version of SS Express Edition SP1 without any problems, even though the above error message indicated I may have login problem. First let me confess that my computer does not have IIS installed, which as I understand is only needed for running the Report Services. Is it necessary for IIS to be up and running while installing SSEE with Advance Services?

The main reason I want to install SSEE with Advance Services is to use the full text search capability. I do not need the Report Services, and was hoping there is an option to turn it off and not require IIS. Is this possible?

Mike

Hi Mike,

You do not need to have IIS installed or running to install Express Advanced as long as you don't need Reporting Services. As far as the error you're getting, we'd really need to check for additional informaiton in the setup log. Could you check that out and get back to the thread with the info from the log?

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Hi Mike,

I am glad to hear that IIS is not required for SQLExpress Advanced installation. The error I got is as follows taken from the summary log file.

Machine : WS2
Product : Microsoft SQL Server 2005
Product Version : 9.1.2040.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_WS2_SQL.log
Last Action : InstallFinalize
Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error Number : 29515

Background information: (OS: Windows XP SP2)

1. Logged in as user with local administrative priviliges.

2. Installed SQL Express RTM a while back, and was able to login to instance and use databases.

3. Attempted to install SQLExpress Advanced CTP without uninstalling SQLExpress RTM. This process is suppose to upgrade the existing installation.

4. *** Installation fails and the sql server setup installation rolls back. *** The previous installation (SQLExpress RTM) is automatically restored, and I am able to login to the sql server.

5. l then try to install SQLExpress CTP. This works perfectly. Note I did not make any changes between steps 4 and 5 (e.g. no reboot, etc.).

Looking through the log files it looks like the SQLExpress Advanced is trying to make an ODBC connection and failing. Why is it trying to use ODBC?

Anyway there is a lot of information in the logs that I do not understand, so it would be better if I could send them to you. (All the log files are in a 1.3M cab file) Please advise.

Thanks,

Mike

|||I am having the same error message also. I previously installed Visual Studio 2005 (not express). Could this have changed the sa password?|||

Hi, I've got the same problem - any ideas?

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=29515&EvtType=lib%5codbc_connection.cpp%40Do_sqlScript%40OdbcConnection%3a%3aconnect%40connect%40x4818

BUTTONS:

&Retry
Cancel

|||I have the same error during setup. I was upgrading a named instance of SSEE 2005 to SSEE w/ Advanced Services.

I used Windows Auth for the install; my windows account is a local admin on the server in question (Win2k Server) and my account has the sysadmin role in SQL Server.

I also tried it using SQL Server Auth with the SA account. That immediately showed the message:

"SQL Server Setup cannot upgrade the specified instance by using SQL Server credentials. You must use Windows Authentication credentials for the upgrade."

So, I find it strange that the setup fails with the message:

"SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information."
(The Error Number in the log summary is 29515)

It says the login failed for user 'sa' even though I used Windows Authentication.

Btw, I used the download posted here: http://msdn.microsoft.com/vstudio/express/sql/download/ Is that still a CTP?
|||More info from the error log:

SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.

Error Code: 0x80074818 (18456)
Windows Error Text: Source File Name: lib\odbc_connection.cpp
Compiler Timestamp: Wed Oct 26 16:37:41 2005
Function Name: OdbcConnection::connect@.connect
Source Line Number: 148

- Context --

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr

Error Code: 18456
MSI (s) (34!D4) [16:38:57:313]: Product: Microsoft SQL Server 2005 -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.

Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Failure Type='Fatal' Error='18456'>
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='203'>
MSI (s) (34:C8) [16:38:57:360]: User policy value 'DisableRollback' is 0
MSI (s) (34:C8) [16:38:57:360]: Machine policy value 'DisableRollback' is 0
Action ended 16:38:57: InstallFinalize. Return value 3.
|||

Seems to be an issue that happens during upgrade.

In order to correctly upgrade from Express Edition to Express Edition with Advanced Services, follow the instructions in the SQL Express blog at: http://blogs.msdn.com/sqlexpress/archive/2006/04/20/UpgradeToAdvanced.aspx

If you've already tried to upgrade and received the error "Login failed for user 'sa'" then you will need to follow the instructions in the SQL Express blog at: http://blogs.msdn.com/sqlexpress/archive/2006/04/20/580312.aspx

Regards,

Mike Wachal
SQL Express team

-
Please mark your thread as Answered when you get your solution.

|||Brilliant!
I ran into the same problem yesterday. Will try to use the blog posts to solve my problem. :)

Kaisa
|||The new version of SQLEXP_ADV worked just fine, I was using an earlier version saved on my CD's from Apr, but I just don't understand why these things just get so hard to fine. Great Job!!!! Keep up the hard work....

Problem installing SQL 2k 32bit on Windows 2003 64bit x86 SP1

I've been having no luck trying to install SQL 2k 32bit on Windows 2003 64bit x86 SP1 - I've found several articles regarding needing to put SP4 on the 64bit OS, but my problem is the SQL 2k 32bit ",,\x86\setup\setupsql" won't run.

I consistantly receive a "...(localuserdir)\Local.ins. Unable to load installaion instructions. Error 703."

And of course, the SP4 setup won't run because there is not an existing SQL Service to upgrade.

Anyone come up against a similar problem?

Thanks!

Are we talking about an X64 machine here? You cant install 32-bit on IA64.

Problem Installing SP1 in Web Farm

I have some concerns about the install process outlined in the readme for SP1. The readme indicates that the database server (the server hosting the ReportServer database) should be upgraded first.
â'The order in which you apply SP1 is important. You must first apply SP1 to the server that hosts the report server database (this updates the database format to the SP1 version). Once you update the database, you can update the report server nodes in any order.â'
My infrastructure looks like this ->
Server 1 & 2 : 2 node NLB running Reporting Services
Server 3: SQL Server 2000 server hosting the ReportServer database (no RS components)
When I install SP1 on the database server (it is not running any RS components â' just hosting the ReportServer database) the install fails with the following error ->
â'The upgrade patch cannot be installed by the windows installer services because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program.â'
When the install on the database server failed, I went ahead and installed SP1 on the servers running Reporting Services â' The install completed and Reporting Services shows the appropriate version number (8.00.878.00) but I didnâ't see any splash screens indicating that the database was being upgraded (as I have when I have applied SP1 on machines running both SQL Server and Reporting Services).
Has anyone had a similar experience upgrading the database server, either in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
Has anyone successfully implemented SP1 on a SQL Server that is not running any RS components?
Thanks,
MarkThe readme seems to be a little confusing. You can only run setup on
machines that RS is installed on, because your DB resides on a separate
machine you do not need to run SP1 setup on this machine.
Here is a good way to upgrade SP1 on a farm.
Turn off the other nodes (turn off IIS and the ReportServer windows service)
Run SP1 install on the one machine that still has IIS and the ReportServer
service running. This will upgrade the DB.
Hitting the vroot for this machine should now work
For each machine in the farm:
Turn on IIS and the ReportServer service
Run sp1 setup
Ensure machine is working properly
Following these steps you will be able to upgrade your farm.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
news:CAF2DC91-11C5-4E76-8ED9-FC99824E6D9F@.microsoft.com...
> I have some concerns about the install process outlined in the readme for
SP1. The readme indicates that the database server (the server hosting the
ReportServer database) should be upgraded first.
> "The order in which you apply SP1 is important. You must first apply SP1
to the server that hosts the report server database (this updates the
database format to the SP1 version). Once you update the database, you can
update the report server nodes in any order."
> My infrastructure looks like this ->
> Server 1 & 2 : 2 node NLB running Reporting Services
> Server 3: SQL Server 2000 server hosting the ReportServer database (no RS
components)
> When I install SP1 on the database server (it is not running any RS
components - just hosting the ReportServer database) the install fails with
the following error ->
> "The upgrade patch cannot be installed by the windows installer services
because the program to be upgraded may be missing, or the upgrade patch may
update a different version of the program."
> When the install on the database server failed, I went ahead and installed
SP1 on the servers running Reporting Services - The install completed and
Reporting Services shows the appropriate version number (8.00.878.00) but I
didn't see any splash screens indicating that the database was being
upgraded (as I have when I have applied SP1 on machines running both SQL
Server and Reporting Services).
> Has anyone had a similar experience upgrading the database server, either
in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
> Has anyone successfully implemented SP1 on a SQL Server that is not
running any RS components?
> Thanks,
> Mark
>|||Thanks Daniel
So even though I donâ't see an â'upgrading databaseâ?¦â' dialog box during SP1 install on the first node â' I can assume that the upgrade has taken place?
Is there anything I can check in the ReportServer db to confirm?
Thanks,
Mark
"Daniel Reib [MSFT]" wrote:
> The readme seems to be a little confusing. You can only run setup on
> machines that RS is installed on, because your DB resides on a separate
> machine you do not need to run SP1 setup on this machine.
> Here is a good way to upgrade SP1 on a farm.
> Turn off the other nodes (turn off IIS and the ReportServer windows service)
> Run SP1 install on the one machine that still has IIS and the ReportServer
> service running. This will upgrade the DB.
> Hitting the vroot for this machine should now work
> For each machine in the farm:
> Turn on IIS and the ReportServer service
> Run sp1 setup
> Ensure machine is working properly
> Following these steps you will be able to upgrade your farm.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mark Barker" <MarkBarker@.discussions.microsoft.com> wrote in message
> news:CAF2DC91-11C5-4E76-8ED9-FC99824E6D9F@.microsoft.com...
> > I have some concerns about the install process outlined in the readme for
> SP1. The readme indicates that the database server (the server hosting the
> ReportServer database) should be upgraded first.
> >
> > "The order in which you apply SP1 is important. You must first apply SP1
> to the server that hosts the report server database (this updates the
> database format to the SP1 version). Once you update the database, you can
> update the report server nodes in any order."
> >
> > My infrastructure looks like this ->
> >
> > Server 1 & 2 : 2 node NLB running Reporting Services
> > Server 3: SQL Server 2000 server hosting the ReportServer database (no RS
> components)
> >
> > When I install SP1 on the database server (it is not running any RS
> components - just hosting the ReportServer database) the install fails with
> the following error ->
> >
> > "The upgrade patch cannot be installed by the windows installer services
> because the program to be upgraded may be missing, or the upgrade patch may
> update a different version of the program."
> >
> > When the install on the database server failed, I went ahead and installed
> SP1 on the servers running Reporting Services - The install completed and
> Reporting Services shows the appropriate version number (8.00.878.00) but I
> didn't see any splash screens indicating that the database was being
> upgraded (as I have when I have applied SP1 on machines running both SQL
> Server and Reporting Services).
> >
> > Has anyone had a similar experience upgrading the database server, either
> in a web farm scenario or a two-server (RS: Server1, SQL: Server2) scenario?
> >
> > Has anyone successfully implemented SP1 on a SQL Server that is not
> running any RS components?
> >
> > Thanks,
> > Mark
> >
>
>

Problem installing setup support files

Hi,
trying to install Reporting Services Enterprise Ed. on a server machine with
configuration:
- Win 2003 Enterprise with SP1
- MS SQL 2000 Server with SP4
- IIS 6 with ASP.NET 1.1
Problem is that when I execute Setup.exe I receive an message: "Error!"
after only 2-3 seconds and thats it! No more info on what the error is or so.
Only option for me is to click Cancel and the installation ends.
This happens when setup tries to install Microsoft SQL Server Reporting
Services Setup Support Files which is the first to happen.
Please, anyone have an idea what this can be or even how to track down the
error?
No errors are reported in Event Viewer.
I have rerun aspnet_regiis just in case, witout any result.
Thanks.Found the problem!
I was running the installation from my local DVD logged in to the server via
Remote Desktop and my local disks shared.
Copied the installationfiles to server harddisk and it installed!
"Gizmo Gizmo" wrote:
> Hi,
> trying to install Reporting Services Enterprise Ed. on a server machine with
> configuration:
> - Win 2003 Enterprise with SP1
> - MS SQL 2000 Server with SP4
> - IIS 6 with ASP.NET 1.1
> Problem is that when I execute Setup.exe I receive an message: "Error!"
> after only 2-3 seconds and thats it! No more info on what the error is or so.
> Only option for me is to click Cancel and the installation ends.
> This happens when setup tries to install Microsoft SQL Server Reporting
> Services Setup Support Files which is the first to happen.
> Please, anyone have an idea what this can be or even how to track down the
> error?
> No errors are reported in Event Viewer.
> I have rerun aspnet_regiis just in case, witout any result.
> Thanks.