Failed connecting to SQL 2005 EXP

Which Altiris article are you referring to?

There are instructions in the KB as to how to setup SQL Express 2005 to use with WPS and I have used these instructions a number of times to create an XP virtual machine on VMWare, running WPS 7 SP3 with SQL Express 2005. However, this is all on one VM machine and not split across different servers.

We need to understand how many different machines you are using to host the different services.

Thank you for your reply. I have downloaded the Word document from Altiris KB (attached)



Here is my scenario:



1. On a Windows XP machine, installed SQL 2005SP1 Exp and installed WPS 7.0 SP3, QA, and EMS. (it is working fine on this machine - I temporary called this machine A)

2. From other machine, created a VM, connected to the WPS share on the machine A, installed WPS network client. Installed successful, but when run the WPS, the connection error happened.



The network client installation option stated that it needed MDAC 2.6 SP2 in order to make connection. I did installed MDAC but no sucess...



Thanks,

TomN

Did you enable named pipes?

Not before. I just enabled it but not sucess either. attached doc.

Unfortunately, I'm not totally au fait with SQL setups, but have you checked that the ODBC connections in your VM are able to communicate with your SQL server using the "Test Connection" button?

Did you originally choose "windows authentication" during setup?

Is there anything else in the KB that might help you?



If not, I suspect your best course of action is to contact Wise support directly, as they have greater internal reference material for SQL issues.

Hi,



TomN...



So you use the local admin account on both machine?

Why do you use two machine?

Do you have same password on both admin account?



/SaiTech

Hi SaiTech,

Sorry for the delay. I've been busy with other testings...



1. On a Wise server (Window XP, WPS7SP3, QA, EMS, and SQL Express) configured to the company Domain and using AD account (added to local Administrator's group). On a different machine also in the same Domain, created a VM machine with clean XPSP2 configured in the WORKGROUP; then connected to the server to install WPS thin client (run from the server) to do the capture.



2. to capture on the clean machine... and this is the procedure for all of my team members to do the capture.



3. It did not make any difference



Thanks,



Question: Does WPS Standard version also requires SQL server?

On your VM, if you are using a local account and the machine is not joined to the domain, how is your VM user account going to be validated on the domain in order to get SQL access?



I was worked in a packaging environment hosted entirely on virtual machines within a large ESX environment, running WPS and SQL, and with all machines part of the same domain. Worked perfectly.

Just ensure that user profiles are not roaming profiles, so that when you roll back the VM to the original clean build, the profile is also rolled back. That ensures the cleanest possible environment for capturing.