I am trying to ThinApp Sql Server 2005 SP 2, but so far have not had success.
I've followed the suggestions in the following links, and the database works fine on my clean PC, but I get errors when I try to run the ThinApp on other machines.
http://209.85.173.132/search?q=cache:http://blogs.vmware.com/thinapp/2008/11/how-to-thinapp.html
For testing, I am starting with a clean copy of 32-bit Windows XP with SP3 and all updates installed (host system is XP x64). I start the ThinApp capture and then run a custom installer that installs SQL Server 2005 Express SP2 on the computer and creates a server instance called SQLEXPRESS_CQSG2 with an sa account and password.
I then install the SQL Server Management Studio SP2 and create the ThinApp using all the defaults including merged isolation mode.
When I attempt to run the management studio on a Windows XP 32-bit box, it starts up but cannot connect to the server instance:
I checked, and the server instance does allow remote connections. I also get connection errors when I try to run the Configuration Manager and the Surface Area Configuration program. Also, attempting to connect to the database using the Native Client ADO provider fails with a connection string (Provider=SQLNCLI;Server=.\SQLEXPRESS_CQSG2;Uid=sa;Pwd=xyzzy) that works fine in a non-ThinApp environment.
I checked the log file in C:\Documents and Settings\Fred\Application Data\Thinstall\Microsoft SQL Server 2005\%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG and it contains:
2008-12-31 13:44:34.43 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2008-12-31 13:44:34.43 Server (c) 2005 Microsoft Corporation.
2008-12-31 13:44:34.43 Server All rights reserved.
2008-12-31 13:44:34.43 Server Server process ID is 3852.
2008-12-31 13:44:34.43 Server Authentication mode is MIXED.
2008-12-31 13:44:34.43 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-12-31 13:44:34.43 Server This instance of SQL Server last reported using a process ID of 2804 at 12/31/2008 12:34:51 PM (local) 12/31/2008 8:34:51 PM (UTC). This is an informational message only; no user action is required.
2008-12-31 13:44:34.44 Server Registry startup parameters:
2008-12-31 13:44:34.44 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-12-31 13:44:34.44 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-12-31 13:44:34.44 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-12-31 13:44:34.49 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-12-31 13:44:34.49 Server Detected 2 CPUs. This is an informational message; no user action is required.
2008-12-31 13:44:34.62 Server Error: 8313, Severity: 16, State: 1.
2008-12-31 13:44:34.62 Server Error in mapping SQL Server performance object/counter indexes to object/counter names. SQL Server performance counters are disabled.
2008-12-31 13:44:34.62 Server Error: 3409, Severity: 16, State: 1.
2008-12-31 13:44:34.62 Server Performance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions.
2008-12-31 13:44:34.77 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.
2008-12-31 13:44:34.80 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-12-31 13:44:34.85 Server Database mirroring has been enabled on this instance of SQL Server.
2008-12-31 13:44:34.85 spid5s Starting up database 'master'.
2008-12-31 13:44:35.07 spid5s Error: 19098, Severity: 16, State: 1.
2008-12-31 13:44:35.07 spid5s An error occurred starting the default trace. Cause: 0x80070050(The file exists.) Use sp_configure to turn off and then turn on the 'default trace enabled' advanced server configuration option.
2008-12-31 13:44:35.10 spid5s Starting up database 'mssqlsystemresource'.
2008-12-31 13:44:35.10 spid5s Error: 824, Severity: 24, State: 6.
2008-12-31 13:44:35.10 spid5s SQL Server detected a logical consistency-based I/O error: insufficient bytes transferred. It occurred during a read of page (1:0) in database ID 32767 at offset 0000000000000000 in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mssqlsystemresource.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
2008-12-31 13:44:35.13 spid5s Error: 945, Severity: 14, State: 2.
2008-12-31 13:44:35.13 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
Using cmd.exe in the ThinApp, I checked and the mssqlsystemresource.mdf file does exist when I CD to c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ and do a DIR.
Could this be some sort of permissions issue?
Any help would be appreciated!
Thanks,
Fred