Question : SQL 2008 Server conflict ... after SYSPREP.

All These on a VMWare (v2) environment:

1. I created a brand new VM1 with MS Server 2008-r2 & SQL Server 2008, applied all the MS updates and appeared to be working just fine.
2. I wanted to use this first VM1 as my base VM for future VM installations
3. Beforing running SYSPREP on this first VM1, I made a copy of VM1 onto another folder.
4. After having the copy, I proceeded running SYSPREP on the original VM1, and renamed this VM as VM-Base2008
5. The reason I ran the SYSPREP is to make copies of this base VM, let it create a new SID, etc. and use it as a new VM.
6. Results:  VM-Base2008 (sysprep'd) works and appears to be running fine after installing my first SQL application on it.   VM1 (the original copy), also appears to be running fine after installing SharePoint 2010 on it.

Problem: Whe I ran both VM1 and VM-Base2008, they both load ok, but SQL Managment Studio 2008 locks up on one, and the Sharepoint 2010 will not load on the other VM .... like there is a conflict on the SQL servers ... I took all the defaults when I installed the SQL 2008 server initially, even the instance name (MSSQLSERVER).

When I ran VM1 by itself things work fine.  When I ran VM-Base2008 SharePoint works fine ... It's just when both are up at the same time.

Can any of you (gurus) give me some leads on where should I start looking for that conflict, are there any settings I should check?

Both VM's are on the same physical Host box.

Any help is greatly appreciated.  Thanks.

Answer : SQL 2008 Server conflict ... after SYSPREP.

Hi,

Since the page directive is not included in the code you have posted i cant see whether you have tried this but there is a property called "MaintainScrollPositionOnPostback" that you can set to true in the page directive which will force the page to maitain the scroll position on postback.

/Carl.