VMware Horizon Community
Reave
Contributor
Contributor

Sql Server

I am working to virtualize sql server 2005 in order to support a virtual application that makes use of it but I am encountering some difficulties.

When I start Sql Server management studio and authenticate using Sql Server Authentication I recieve the following error.

“A network-related or instance-specific error occurred whileestablishing a connection to SQL Server. The server was not found orwas not accessible. Verify that the instance name is correct and thatSQL Server is configured to allow remote connections. (provider: SQLNetwork Interfaces, error: 26 – Error Locating Server/InstanceSpecified) ”

I have attached a graphic of the origional error message.

I am using the following script gleaned from the forums to force to the sandbox all of the databases within the package as suggested in other posts.

'SQL Force to sandbox script

Sub ForceToSandbox(FileName)

Const ForAppending = 8

Dim Fso, F, Ts

Set Fso = CreateObject("Scripting.FileSystemObject")

Set F = Fso.GetFile(ExpandPath(FileName))

Set Ts = f.OpenAsTextStream(ForAppending)

Ts.Close()

MsgBox(FileName)

End Sub

Function OnFirstSandboxOwner

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\distmdl.ldf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\master.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mastlog.ldf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\model.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\modellog.ldf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdbdata.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\msdblog.ldf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\mssqlsystemresource.ldf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\tempdb.mdf")

ForceToSandbox("%ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Data\templog.ldf")

End Function

Additionally, I am following the portion of the step by step guide:

Change the folder isolation level for "%AppData%\Microsoft\Crypto\RSA" from FULL to MERGED by editing the ##Attributes.ini file in that directory and changing "DirectoryIsolationMode=Full" to "DirectoryIsolationMode=Merged".

Though I am making the change in %Common AppData%\Microsoft\Crypto\RSA because the folder path doesn't exist in %AppData%.

My Sql Server settings:

named instance: ML

Use the built in System Account: Local System

Authentication mode: Mixed Mode Authentication

Any advice for rectifying this issue is appreciated.

Reply
0 Kudos
3 Replies
admin
Immortal
Immortal

When doing the SQL Server installation during SetupCapture, you should set the account that the service will be running as to the name of the user that's doing the install (usually "Administrator"). I get the impression that you left it as LocalSystem?

Also shut down the instance before doing the postscan.

There are probably log files in %ProgramFilesDir%\Microsoft SQL Server\MSSQL.1\MSSQL\Logs, perhaps they'll give a clue? If there's a message in there mentioning SSL I'm pretty sure that the problem is with the account as mentioned above.

Reply
0 Kudos
Reave
Contributor
Contributor

I performed the capture again. This time I used the user name that I was logged in as to perform the install. I did notice that this drifted the Microsoft/Crypto/RSA folder into the %appdata% folder instead of %common appdata% so I was able to more faithfully carry out the directions from the step by step guide for sql. However I am still getting the same error message when I launch sql server management studio wheather I set the package to merged or writecopy.

Reply
0 Kudos
Reave
Contributor
Contributor

Okay, repeated the test again. I was successful using a default instance on sql server 2005 express.

Does the version of sql server 2005 I use affect wheather or not it will function?

Or does it have to do with wheather or not I used a named instance or the default one.

Reply
0 Kudos