ThinApp SQL Server 2005 Express

I try to ThinApp Sql Server 2005 SP2, but so far have no success.

I followed the suggestions in the following links and the database works very well on my own 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

http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 1006992 & sliceId = 1 & docTypeID = DT_KB_1_1 & dialogID = 12638526 & StateID = 1% 200% 2012642237

http://KB.VMware.com/selfservice/microsites/search.do?cmd=displayKC & docType = kc & externalId = 154-154671xml & sliceId = & docTypeID = DT_COMMUNITIES_1_1 & dialogID = 12646964 & stateId = 1% 200% 2012654147

For testing, I start with a clean copy of Windows XP with SP3 and all updates installed 32-bit (host system is XP x 64). I start capturing ThinApp and run a custom Setup, which installs SQL Server 2005 Express SP2 on the computer and creates a server instance called SQLEXPRESS_CQSG2 with an account his and the password.

I then install the SQL Server Management Studio with SP2 and create the ThinApp using all the flaws, including the merged isolation mode.

When I try to run management studio on a Windows XP 32-bit machine, it starts, but it is impossible to connect to the server instance:

http://communities.vmware.com/servlet/JiveServlet/downloadImage/4852/SqlServerError.JPG

I checked, and the server instance does not allow remote connections. I also have connection errors when I try to run the Configuration Manager and the Configuration of the Surface program. In addition, attempts to connect to the database using ADO Native Client provider fails with a connection string (provider = SQLNCLI; Server =. \SQLEXPRESS_CQSG2; UID = sa; Pwd = xyzzy) that works very well 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 X 86)

February 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 process ID is 3852.

2008-12-31 13:44:34.43 server authentication mode is MIXED.

2008-12-31 13:44:34.43 messages from server record SQL Server in the 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 is a latest report by using a process ID of 2804 at 31/12/2008 12:34:51 (local) 2008-12-31 20:34:51 (UTC). This is an informational message only; no user action is required.

2008-12-31 13:44:34.44 registry server 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 e Server - 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 starts at the normal base priority (= 7). It is an informational message only. No user action is required.

2008-12-31 13:44:34.49 Server has detected 2 processors. 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 the mapping of the index of meter/performance object SQL Server for counter/object 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 the shared server performance counter configuration memory 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 allocation of dynamic locking using the server. Initial allocation of blocks of lock of 2500 and 5000 per node lock owner. It is an informational message only. No user action is required.

2008-12-31 13:44:34.80 Server Scheduler CPU ID time stamp counter 1 is not synchronized with the other processors.

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 start 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 from the default trace. Cause: 0 x 80070050 (the file exists). Use sp_configure to turn on and turn off then on the 'default trace enabled' Advanced Server configuration option.

2008-12-31 13:44:35.10 spid5s start database 'mssqlsystemresource '.

2008-12-31 13:44:35.10 spid5s error: gravity 824,: 24, State: 6.

2008-12-31 13:44:35.10 spid5s SQL Server has detected an e/s logic based consistency error: insufficient bytes transferred. It occurred during a read of page (1:0) in the 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. It is a serious condition that threatens the integrity of data and should be corrected immediately. Perform a complete database consistency check (DBCC CHECKDB). This error can be caused by several 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 exists when I CD c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\ and DIR.

Could be some sort of permissions problem?

Any help would be appreciated!

Thank you

Fred

I saw him recently. It is due to a bug in ThinApp. The solution is to force the mssqlsystemresource.mdf and mssqlsystemresource.ldf files to the bin to sand. You can do this for example by starting a virtual cmd.exe, then:

CD \Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA

Rename the mssqlsystemresource.mdf temp

Rename the mssqlsystemresource.mdf temp

Rename mssqlsystemresource.ldf temp

Rename mssqlsystemresource.ldf temp

Tags: VMware

Similar Questions

Maybe you are looking for