We’ve just now created a VM environment to test upgrades on. I can log into the test DB just fine, but trying to log into the VM’s version of the production environment results in this error:
What do I do about this? Should I just run the 10.2 upgrade on the test DB and not worry about the fake production environment?
Stop and start the application pool in IIS and thereafter restart the task agent for this particular application server.
Also ensure the correct credentials are defined in the application pool as you have mentioned the environment is a clone of the production so make sure the domain account is also working in the cloned environment.
I checked all of that and all the credentials appear to be fine, but it still won’t connect.
I’m curious about why the test environment works and the production one doesn’t. I’ve also noticed before that certain features appear to be disabled in the test environment, like posting invoices. Is there a setting that changes the connection properties of an environment, which keeps the test environment isolated?
How are the production and test environments configured, are both in the same server, separate servers.
Are both the production and test on the same network? if yes then there are chances of test environment connecting to production if configurations are not done correctly in system agent and task agent.
Test environments are recommended to be isolated from the production network and this can easily be achieved using VMs. VMs allow creation of isolated virtual networks and clone of production can then be used for testing.