Setting up a Pre-Production Test Environment

re: Setting up a Pre-Production Test Environment

Trana010 — Thu, 19 Jan 2012 03:13:53 GMT

So I did have another crack at it with a DC built especially for the task as above and this time using Hyper-V guests which was a lot smoother than VirtualBox for these purposes. As mentioned before my SQL DBs are located on a dedicated server in the production environment and I couldn't use Disk2VHD on that because of the EFI System partition on it.

But following the outlined steps in the blog, I only needed to do one additional step on my test SQL server, enable CLR as per this:

strangenut.com/.../how-to-enable-clr-stored-procedures-on-sql-server-2005-and-2008.aspx

So now its time for 2012 RC! :)

re: Setting up a Pre-Production Test Environment

Trana010 — Thu, 01 Dec 2011 23:41:41 GMT

Well no, 5723 doesnt work on my production server either though. On the test server the firewall is turned off for all networks (same as production server), but just in case I created and outbound and inbound rule allow everything from and too everything, makes no difference.

I am going on 1 weeks leave next week but I am thinking when I can find the time, I might just start from scratch with a different approach.

Thanks for your help, but I think theres something fundamentally wrong with my test setup.

re: Setting up a Pre-Production Test Environment

Fletcher Kelly — Thu, 01 Dec 2011 06:39:09 GMT

Can we please run a simple test,

I just want to confirm that port 5724 and 5723 are open.

Can you please run a simple telnet command to test this.

re: Setting up a Pre-Production Test Environment

Trana010 — Thu, 01 Dec 2011 05:58:59 GMT

Yes, SQL server has the same hostname and SQL instance name.

In the Ops Mgr Event log,

1. OpsMgr SDK Service: The System Center Data Access service has started.

2. Lfx Service: Starting Lfx sub service

3. OpsMgr SDK Service: The System Center Data Access service has reestablished database connectivity.

4. Lfx Service: StartMonitoring: started originally:False

5. (Warning) Lfx Service: Errir starting Lfx service. Tried times: 1

Error message:

The data access service is either not running or not yet initialized. Check the event log for more information.Stack trace.....lots of XML code...

Error message:

Could not connect to net.tcp://localhost:5724/DispatcherService. The connection attempt lasted for a time span of 00:00:02:0321500. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:5724

Server stack trace....

6. Same as 4

7. Same as 5 and it continues like that for 11 attemps

X. Lfx Service: Could not start Lfx sub service with all the retries

Y: OpsMgr SDK Service: The System Data Access service failed due to an unhandled exception.

The service will attempt to restart.

Exception:

Microsoft.EnterpriseManagement.Common.SdkServiceNotInitializedException: The Data Access service has not yet initialized. Please try again....

re: Setting up a Pre-Production Test Environment

Fletcher Kelly — Wed, 30 Nov 2011 06:35:05 GMT

Did you give the SQL the same server name and instance name as your original / prod environment?

re: Setting up a Pre-Production Test Environment

Travis Wright MSFT — Wed, 30 Nov 2011 05:26:39 GMT

Check the Operations Manager event log on the SCSM server for information on why the Data Access Service wont start.

re: Setting up a Pre-Production Test Environment

Trana010 — Wed, 30 Nov 2011 05:20:23 GMT

I tried to do something similar, I made VHDs from my DW, SM and DC servers with disk2vhd, I couldn't do this on the SQL server because of a EFI System partion, so I built a new SQL server for the testing. I set these up in VirtualBox and I have them communicating fine there.

But when trying to launch the SCSM Console it fails with:

Failed to connect to server 'smserver.domain.local'

The Data Access service is either not running or not yet initialized.

in the SM server I got the Data Access Service terminated unexpectedly on every attempt to launch the console, on the SQL server I got a corresponding security log audit success event that the SCSM service account I use is logged off, so the communication there, but something else is wrong.

I've redone the SPN records.

Originally I was using SQL Express, but when I remembered SCSM requires full SQL I reinstalled that (trial).

the SCSM service account is SA in SQL and local admin windows group on the SQL server.

Any ideas?

re: Setting up a Pre-Production Test Environment

Fletcher — Wed, 09 Nov 2011 06:22:12 GMT

Hi Travis,

Thanks for posting this for me.

I will try to assist with questions here as well.

re: Setting up a Pre-Production Test Environment

Steve Beaumont — Tue, 08 Nov 2011 18:50:16 GMT

Not tried it yet in a Hyper-V environment, but in an ESX environment, simply cloning the VM's (DC, SM, DW, SQL) and changing the NIC's so they're on an isolated virtual switch works really well.

If you have SCVMM, I can't see it being any different, except maybe the network would need some tweaking with VLAN tagging etc to isolate it a bit more.