I've heard that this might be a bug in the installer in 5.2. There is some configuration where the repository app.config may be using one connection string to the database while an individual model is using a different one. It is required by SQL that snapshot isolation not use DTC and thus multiple connections with different strings causes this error.
It is a requirement that the configuration for repository web application in web.config match the models that are installed. This should be validated at run time but it appears our installer does not validate this... I suspect this occurs when model manager web is installed with different sql credentials then model manager data.
Check the Repository.Website\web.config on the vCAC Model Manager server/s at the path <drive letter> \Program files 9x86) \VMware\vCAC\Server\Model Manager Web\ for the setting below...
<repository server="localhost" database="vCAC" store="security.xml" />
Make sure the server, database and authentication setting match that in the table below (case is important here also) ...
Data Source=localhost;Initial Catalog=vCAC;Integrated Security=True;MultipleActiveResultSets=True
If they don't match, probably easiest to manually modify both to use windows authentication and restart iis and check if the issue persists. If this resolves the issue and you wish a different configuration, fool around with the settings some more and validate that this still works.
very appreciate for your help
if i make sure model manager web installed using the same SQL credentials as model manager data. this issue should be resolved, right?
Do you heard when this bug will be resolved ?
I am experiencing the same error. We are using AzMan and Active Directory as the repo for authentication. When we try and provision into vCD we get the following error:
System.Data.EntityException: The underlying provider failed on Open. ---> System.InvalidOperationException: Transactions with IsolationLevel Snapshot cannot be promoted.
Have you been able to resolve?
I've got the same issue as described above. Anyone been able to resolve it yet?
I have solved the problem.
In my case the vCAC database was installed with different credentials than the vCAC service running under Windows Server. Re-installing the vCAC with correct credentials fixed the issue for me.
I think Marek has the right answer to the root cause, the installer should not allow you to use different credentials. If you want a workaround without reinstalling, see my earlier post.
I'm having the same problem and reinstalling vCAC 5.2 isn't an option as I have hotfix 5 and FP2 installed on top and the whole environment is distributed so reinstalling would take days. It looks like the database was installed with a SQL service account, so how would i change the database to use the vCAC service account?
I remembered the simple sql command sp_changedbowner
Phil you are my hero
Fixed the problem and saved me days of reinstalling.