Cant run SQL Server 2000 Developer on XP MCE

I started with SQL Server 2005 Express and created a database. Due to circumstances I needed SS 2000. Uninstalled SS 2005 and installed SS 2000 without incident. I already had SS 2000 Enterprise Manager running with other client databases registered.

When I went to Ent Mgr and tried to register my new SS 2000 instance, I got this error: "A connection could not be established to LOYDSLAPTOP. Reason: SQL Server does not exist or access denied. ConnectionOpen (Connect()). Please verify the server is running and check your SQL Server registration properties (by right-clicking on the LOYDSLAPTOP node) and try again."

I have verified that the following services are both running: MSSQL$SQLSERVER2000 and SQLAgent$SQLSERVER2000.

I am certain that I used the sa user with password originally entered when I installed SS 2000 when I tried to register/connect to the local instance of SS. Plus I also tried to connect using the domain user and password entered when I installed SS and got the same error message.

What am I doing wrong? What do I need to change?

Thanks for any help anyone can offer.Shouldn't you use MSCE to run MSSQL SERV 2000 in Windows XP ?|||Not sure what you mean. I googled MSCE and all I got were misspellings of MCSE, or perhaps that is a previous certification from Microsoft. I called MS tech support and they told me that Win XP MCE was not a supported OS, so I guess I'm hosed on that.

Thanks anyway for trying.|||Sorry for the typo, I meant MSDE, and I can tell you it works. I use it on my xp.

http://www.microsoft.com/downloads/details.aspx?familyid=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en|||Ortho,

Thanks for the info. That would have been a great suggestion. I am going to try and get the vendor to take back the SQL Server 2000 Developer Edition and trade it for a 2005 DE. I have already uninstalled the SS 2000 and reinstalled 2005 Express. Also, the hosting company was gracious enough to move us to a SS 2005 server and the backup file I created previously with 2005 Express worked beautifully, so I guess my problems are solved - except for getting my client's costs for the SS 2000 DE put to better use.

Thanks again for the help.|||2005 Express is the equivalent of MSDE but in 2005 version.

Can't install SQL Server Express

Hi all,

I've been trying all day to install SQL Server Express edition on my development machine, I 've uninstalled other Express Editions that I have previously installed, at least none show in add/remove programs. When i try to run the setup program i get the message that i have incompatible programs still installed. I don't know what they would be. None are listed in the program list as I have said. I tried to run the uninstallbeta program on the SQL Server Express page, but I keep getting an error that the "framedyn.dll" cannot be found, reinstalling the application may help! lol !

Any idea's ?

Thanks in advance.

I would make sure that the OS is upto date first, then install the .net framework 2.0 from the update site... after that install the sql native client from the ms download site... if this all works then try the database engine install.

|||

Hi,

Removing and reinstalling some programs appears to leave behind a number of redundant entries in the registry at times, particularly with Beta versions.

I had similar problems where I followed all the procedures, had no references in the Add/Remove programs list, but still was unable to install a later version because of previous versions still installed.

The solution for me was when I found out about a utility download which did in fact remove those entries. Its called MS Window Install Clean Up Utility and can be downloaded from http://support.microsoft.com/default.aspx?scid=kb;en-us;290301.

Hope this is helpful

John

|||

You can also check out my last post in http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=483507&SiteID=1, which details a more manual process for removing left behind products.

One warning about the Windows Installer Cleanup Utility - This does not uninstall products from your computer, it simply removes the registry keys that make products appear in the Add Remove Programs list. You should only use this tool if you're are absolutly sure that the products listed in ARP are really gone but the registry is in error.

Hint: If your setup log indicates that an earlier version is there, it really is there and the cleanup utility will not help you.

Regards,

Mike Wachal
SQL Express team

-
Mark the best posts as Answers!

Cant get SQL Express Installed

Hi-

I had previously had VS2005 Beta installed from my MSDN discs. When it expired, I uninstalled it and downloaded VWD Express to install. VWD installed fine, but the SQL Server Express will not install. The VWD install package doesn't give me any feedback, just says it failed. I tried dowloading and installing SQL Express separately, and it tells me that I have to uninstall all components from other versions. I have done that, but still wont install. If I use the uninstall utility on the website, it tells me it can't find any components, and all of the components listed in the manual uninstall instructions are missing, so I can't find anything further to uninstall. (FYI: I'm running XP Pro SP2).

I'm wondering if a registry setting or something didn't get updated on uninstall. I see a registry folder for "Microsoft SQL Server" but I do not know if this could be getting in the way.

Any help would be appreciated.

-Moz

I guess the issue is caused by imcompletely uninstalled VS2005 beta components. You can find SQL Server setup logs under the "%ProgramFiles%\Microsoft SQL Server\90\Setup\Bootstrap\LOG\Files" folder. However the logs are always verbose to read. So it may be better to uninstall all existing VS2005 components completely, please refer to this article:

http://msdn.microsoft.com/vstudio/support/uninstall/default.aspx

|||

Yeah, I followed the uninstall instructions, but none of the programs to uninstall are in my list. I looked at the logs (thanx for the lead on that) and it appears that the errors are thrown when it loads the msi.dll. The errors in the log indicate that it's finding incompatible versions of the following:

Microsoft SQL Server 2005 CTP|||

I got this straightened out. Nothing was working, but I stumbled on this:

http://blogs.msdn.com/astebner/archive/2005/10/30/487096.aspx

and the steps and tools he provided did the necessary clean up for me, after which I was able to get the express edition installed.

Thanx for the help!

-Moz

Can't get Reporting Services working after reinstall

I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.

The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.

How can I debug this installation?

Check for any other information on windows event log.

Also check under the services whether thye have been started successfully.

|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL

EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__

I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".

sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.

When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.

(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?

One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?

Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application

Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.

What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.

I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.

Can't get Reporting Services working after reinstall

I had to make room on the system partition so I uninstalled SQL 2005 Ent. and reinstalled it in a different partition, which is mounted in c:\apps. Since doing this, although MSSQL works fine, RS does not respond. During the reinstall, Setup reported that RS was "installed but not configured". I ran the RS Configuration Mgr and went through the config sequence. However, on the Initialization page, which has a red 'x' in the left panel, the local server is not listed -- the grid is empty.

The RS service is running, using the same credentials as MSSQL, the admin account .\SQLExec. It logs a normal startup in the Event Log. However, on visiting http://localhost/Reports, I get a message saying that Reporting Services is not responding. SP2 installed OK on the system, and reported that all components were upgraded.

How can I debug this installation?

Check for any other information on windows event log.

Also check under the services whether thye have been started successfully.

|||MSSQL, SSRS, SQL Agent, and IIS are running. I did see some interesting messages in the Application Log:
__
EventID 18456: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'." from MSSQL

EventID 107: "Report Server (MSSQLSERVER) cannot connect to the report server database." From Reporting Svcs.
__

I check in SQL Mgt. Studio: 'NT Authority\Network Service' is set up as a SQL login. The account is in the dbo and RSExecRole roles in the ReportServer database. In the RS Config Mgr, this account is shown as the ASP.NET Service account. The Report Server and Report Manager are both set to "Default Application Pool".

sp_who shows that the 'NT Authority\Network Service' login IS connected to the ReportServer database, along with two other connections to this db from the SQL Service account, .\SQLExec, which is used by all SQL-related services.

When I visit http://localhost/Reports, I now get the message: "Key not valid for use in specified state.

(Exception from HRESULT: 0x8009000B) (rsRPCError)". What does this mean?

One thing I recall seeing when I created the ReportServer database in the RS Configuration Mgr was a warning (yellow '!') saying it was "unable to access internal information" about the installation to verify the connection. Is this a clue?

Any advice how to proceed?|||Further searching revealed this may have to do with a crypto key left over from the prior installation, found under "C:\Documents and Settings\SQLExec\Application

Data\Microsoft\Crypto\RSA" in a file matching "1aedd7b5699f3d6a88e354100b596aae*" Advice was to delete this file and recreate it using the 'rsactivate' utility, which I cannot find. The discussion I found pertained to SSRS 2000 and not in 2005.

What's the correct way to fix this problem in Reporting Services 2005?|||Deleting the 1aedd* key file corrected the problem. I uninstalled SSRS, deleted the old RS databases, deleted the key file, reinstalled SSRS, reapplied SP2. After doing this, each step in the Reporting Svcs Config Mgr then worked correctly.

I would rate this as a serious problem with either SQL Setup or the RS Config Mgr if neither can diagnose nor correct the problem. If I hadn't stumbled across mention of the 1aedd* file on someone's blog I would not have been able to get Reporting Services to work following the reinstallation of MSSQL and its components.