Don't know if this is the appropriate forum...
I have encountered a showstopper problem during installation. I have installed SSEE on a fresh XP, all the checks but memory requirements passed. In the final stage of the install, during the "real work", the Client Component installation failed due to missing ASP.NET state service (? spelling). After the failure the installation continued, but marked both the db engine and the management studio failed. Despite this, management studio was installed and later I have removed it with the control panel applet.
I have found a service (executable: aspnet_state.exe), started it and retried the installation. It failed again so I have removed everything installed except the VSS writer and started it again. This time the installation completed (and finally got BIDS).
Is it enough to start this ASP service manually for a painless install? I don't want to play this "on the field" ever...
I'd need to see the install log from a failed attempt to really understand the problem. This is the first time I've heard mention of the asp.net state service, so this doesn't seem like a common issue. We should get to the bottom of what is really happening before you start trying to start random services on your customers computers.
Mike
|||Is earlier install logs kept? There were two attempts after it, one successfull and one uninstall. At the end of the first failed attempt the installer sent an error report on a form looked like the standard error reporting form - had the installer an unhandled exception or was it my installation feedback?|||Mike,
I hate to post in someone elses thread, but this sounds like the exact same issue I am having. Here is the ERRORLOG:
2007-04-30 14:15:39.88 Server Microsoft SQL Server 2005 - 9.00.2050.00 (Intel X86)
Feb 13 2007 23:02:48
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 (Build 2600: Service Pack 2)
2007-04-30 14:15:39.88 Server (c) 2005 Microsoft Corporation.
2007-04-30 14:15:39.88 Server All rights reserved.
2007-04-30 14:15:39.88 Server Server process ID is 2088.
2007-04-30 14:15:39.88 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-04-30 14:15:39.88 Server This instance of SQL Server last reported using a process ID of 3108 at 4/30/2007 2:08:46 PM (local) 4/30/2007 6:08:46 PM (UTC). This is an informational message only; no user action is required.
2007-04-30 14:15:39.88 Server Registry startup parameters:
2007-04-30 14:15:39.88 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-04-30 14:15:39.88 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-04-30 14:15:39.88 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-04-30 14:15:39.93 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-04-30 14:15:39.93 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-04-30 14:15:40.10 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-04-30 14:15:40.19 Server Could not query the FIPS compliance mode flag from registry. Error 2(The system cannot find the file specified.).
2007-04-30 14:15:40.26 Server Database mirroring has been enabled on this instance of SQL Server.
2007-04-30 14:15:40.27 spid5s Starting up database 'master'.
2007-04-30 14:15:40.30 spid5s Error: 5118, Severity: 16, State: 1.
2007-04-30 14:15:40.30 spid5s The file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2007-04-30 14:15:40.30 spid5s Error: 5118, Severity: 16, State: 1.
2007-04-30 14:15:40.30 spid5s The file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2007-04-30 14:15:40.32 spid5s Error: 5118, Severity: 16, State: 1.
2007-04-30 14:15:40.32 spid5s The file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
2007-04-30 14:15:40.32 spid5s Error: 5118, Severity: 16, State: 1.
2007-04-30 14:15:40.32 spid5s The file "c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf" is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.
I went into the Computer Management console and tried to restart the SQLEXPRESS service (SQL Server Active Directory Helper also) and it gives me "server-specific error code 3417"
Thanks in advance,
Nick
|||According to the end of your log your problem is that your database is in a compressed folder (usually blue letters in Explorer). I think you should uncompress the c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA folder (right-click on the folder, Properties, Special button and uncheck). Or mark it as a read-only database but I don't think you want to do that.|||All your logs should be sitting in C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files. They are number sequentially and you can also use the create date to identify the correct log. The standard error reporting dialog does not collect personal informaiton, nor does it collect the install logs, so I can access anything related to that.
MIke
|||Regarding Nick's issue - We don't support installing to compressed folders so you'll need to uncompress before doing any install/upgrade.
Mike
|||There is no "Special" button|||"Unfortunatelly" I have a hungarian XP so the button label re-translation failed. It is the button on the right side of attributes read only and hidden.
Here is an official description:
To set the compression state of a folder or file
1.
In My Computer or Windows Explorer, right-click the file or folder to compress or decompress.
2.
Click Properties to display the Properties dialog box.
3.
On the General tab, click Advanced.
4.
In the Advanced Attributes dialog box, select or clear the Compress contents to save disk space check box and then click OK.
5.
In the Properties dialog box, click OK.
6.
If the compression state was altered for a folder, in the Confirm Attribute Changes dialog box, select whether to make the compression apply only to the selected folder or to the selected folder and all its files and subfolders. Click OK when done.
Note Windows XP Professional can compress closed paging files. However, when you restart Windows XP Professional, the paging files revert to an uncompressed state. For information about paging files, see the topics on virtual memory in Windows XP Professional Help.
You can set Windows Explorer to display alternate colors for compressed files and folders by using the following procedure:
To display alternate colors for compressed files and folders
1.
In My Computer or Windows Explorer, click the Tools menu, and then click Folder Options.
2.
On the View tab, select the Show encrypted or compressed NTFS files in color check box.
3.
Click OK to return to Windows Explorer or My Computer.
I was having a similar problem, only that for me I could not restart the service after it had stopprd.
Setting permissions on the ...sql server\MSSQL1\data folder sorted me out.
I granted full control on the folder to the machine\users group.
No comments:
Post a Comment