Handling Database failure in Write-Behind
Hi,
In the link mentioned below it is mentioned that "The application is somewhat insulated from database failures: the Write-Behind feature can be configured in such a way that a write failure will result in the object being re-queued for write"
http://coherence.oracle.com/display/COH35UG/Read-Through,+Write-Through,+Write-Behind+and+Refresh-Ahead+Caching
I wanted know how write behind can be configured so as to insulate it from database failures. How can it be configured so that in case of db failure object is re-queded for write
Thanks,
Sudhir
Requeuing can be enabled by setting the write-requeue-threshold to the maximum number of expected entries
that will exist in the queue when it is time to write the data to the database.
A complete example can be found here: http://middlewaremagic.com/weblogic/?p=5954
Look for the cache configuration section.
Similar Messages
-
Write behind with Coherence, What happens if database failover?
When write-behind with coherence tries to delete, update or insert into database but the Oracle database is shutdown, when I start again the database, So when i try insert again in the database show me this error in the cache server:
2009-11-23 23:55:07.926/255.935 Oracle Coherence GE 3.5.2/463 <Error> (thread=WriteBehindThread:CacheStoreWrapper(com.oracle.coherence.handson.DBCacheStore), member=1): (Wrapped: Load failed: key=catalog50) java.sql.SQLException: Closed Connection
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.oracle.coherence.handson.DBCacheStore.load(DBCacheStore.java:64)
at com.oracle.coherence.handson.DBCacheStore.store(DBCacheStore.java:77)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheStoreWrapper.store(ReadWriteBackingMap.java:4338)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheStoreWrapper.storeInternal(ReadWriteBackingMap.java:4064)
at com.tangosol.net.cache.ReadWriteBackingMap$WriteThread.run(ReadWriteBackingMap.java:3731)
at com.tangosol.util.Daemon$DaemonWorker.run(Daemon.java:714)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.SQLException: Closed Connection
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3127)
at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:3042)
at com.oracle.coherence.handson.DBCacheStore.load(DBCacheStore.java:50)
... 6 more
How i can reestablish the database connection without restart my cache server?
Please Help me!!!
Sorry for my english.Hi,
It looks like you are using com.oracle.coherence.handson.DBCacheStore.
http://download.oracle.com/docs/cd/E13924_01/coh.340/e14135/cohjdev.htm
If so, then I think that you could simply change the following method in the DBCacheStore ...
public Connection getConnection()
if (m_con == null || m_con.isClosed())
configureConnection();
return m_con;
}Thanks,
Tom -
Write-Behind batch behavior in EP partition level transactions
Hi,
We use EntryProcessors to perform updates on multiple entities stored in the same cache partition. According to the documentation, Coherence handles all the updates in a "sandbox" and then commits them atomically to the cache backing map.
The question is, when using write-behind, does Coherence guarantee that all entries updated in the same "partition level transaction" will be present in the same "storeAll" operation?
Again, according to the documentation, the write-behind thread behavior is the following:
The thread waits for a queued entry to become ripe.
When an entry becomes ripe, the thread dequeues all ripe and soft-ripe entries in the queue.
The thread then writes all ripe and soft-ripe entries either via store() (if there is only the single ripe entry) or storeAll() (if there are multiple ripe/soft-ripe entries).
The thread then repeats (1).
If all entries updated in the same partition level transaction become ripe or soft-ripe at the same instant they will all be present in the storeAll operation. If they do not become ripe/soft-ripe in the same instant, they may not be all present.
So, it all depends on the behavior of the commit of the partition level transaction, if all entries get the same update timestamp, they will all become ripe at the same time.
Does anyone know what is the behavior we can expect regarding this issue?
Thanks.Hi,
That comment is still correct for 12.1 and 3.7.1.10.
I've checked Coherence APIs and the ReadWriteBackingMap behavior, and although partition level transactions are atomic, the updated entries will be added one by one to the write behind queue. In each added entry coherence uses current time to calculate when each entry will become ripe, so, there is no guarantee that all entries in the same partition level transaction will become ripe at the same time.
This leads me to another question.
We have a use case where we want to split a large entity we are storing in coherence into several smaller fragments. We use EntryProcessors and partition level transactions to guarantee atomicity in operations that need to update more than one fragment of the same entity. This guarantees that all fragments of the same entity are fully consistent. The cached fragments are then persisted into database using write-behind.
The problem now is how to guarantee that all fragments are fully consistent in the database. If we just relly on coherence write-behind mecanism we will have eventual consistency in DB, but in case of multi-server failure the entity may become inconsistent in database, which is a risk we wouldnt like to take.
Is there any other option/pattern that would allow us to either store all updates done on the entity or no update at all?
Probably if in the EntryProcessor we identify which entities were updated and if we place them in another persistency queue as a whole, we will be able to achieve this, but this is a kind of tricky workaround that we wouldnt like to use.
Thanks. -
Write behind exception and recovery
Hi all,
I am working on write behind part in equity trading system. I know that cache store operation will eventually be thrown away if no of retry exceed write-requeue-threshold. However, this is not acceptable as DB must sync with caches at least at day end. For some more complicated caches, we use cache store implementation and Hiberate for simple cache. I am thinking to capture the sql statements that failed during the day and finally at day end, manually fix issues (egDB issue or others) then have them executed.
Questions:
1. Is this a good approach for handling the scenario? If yes, any way I can capture the statements and write to file for running in SQL plus for example in case of Hiberate?
2. Is there any out of box mechanism in Coherence for recovering write-behind queues in case of WHOLE cluster fail (not node fail).
Henry922963 wrote:
Hi all,
I am working on write behind part in equity trading system. I know that cache store operation will eventually be thrown away if no of retry exceed write-requeue-threshold. However, this is not acceptable as DB must sync with caches at least at day end. For some more complicated caches, we use cache store implementation and Hiberate for simple cache. I am thinking to capture the sql statements that failed during the day and finally at day end, manually fix issues (egDB issue or others) then have them executed.
Questions:
1. Is this a good approach for handling the scenario? If yes, any way I can capture the statements and write to file for running in SQL plus for example in case of Hiberate?Hi Henry,
There are a few caveats you need to care about but in general it is possible.
Not necessarily SQLs but serialized entries would probably be simpler to work with when you try to restore them.
Also, you have to be aware that Coherence may fail to write an entry to the DB but at retry it may try to write a new entry. If it succeeds, you have to be able to figure that out that the earlier failure must not be reexecuted.
In effect, you should have per-entry versioning in the database and you should check versions of the entity in the database upon writing both from the cache store and also from your end-of-day retry logic.
2. Is there any out of box mechanism in Coherence for recovering write-behind queues in case of WHOLE cluster fail (not node fail).
No, nothing like that comes out-of-the-box, if you lost a partition, you lost your write-behind-enqueued entries, too. You could log your failed writes to disk though as you indicated above.
Best regards,
Robert -
How to limit Write-Behind batch
We have a scenario:
we use read-write-backing-map-scheme having write-delay 60s.
System insert a lot of data and then time comes to write data coherence find 40-50 k of unsaved record and pass them all to cachestore.
Due to data volume or database busyness cashstore may work some time several seconds for instance.
<read-write-backing-map-scheme>
<scheme-name>TicketDatabaseScheme</scheme-name>
<scheme-ref>DefaultDatabaseScheme</scheme-ref>
<!--<write-delay>1m</write-delay>-->
<cachestore-scheme>
<class-scheme>
<class-name>com.griddynamics.ticketon.app.dao.coherence.TicketCacheStore</class-name>
</class-scheme>
</cachestore-scheme>
</read-write-backing-map-scheme>
<read-write-backing-map-scheme>
<scheme-name>DefaultDatabaseScheme</scheme-name>
<internal-cache-scheme>
<local-scheme>
<scheme-ref>LocalScheme</scheme-ref>
</local-scheme>
</internal-cache-scheme>
<write-delay>60s</write-delay>
</read-write-backing-map-scheme>
In the case we experience "Terminating guarded execution" followed by service termination.
2010-02-11 09:26:52.223/511.457 Oracle Coherence GE 3.5.2/463 <Error> (thread=DistributedCache:TicketonCache, member=2): Terminating guarded execution (due to hard timeout 1924ms ago) of Daemon{Thread="Thread[WriteBehindThread:CacheStoreWrapper(com.griddynamics.ticketon.app.dao.coherence.TicketCacheStore),5,WriteBehindThread:CacheStoreWrapper(com.griddynamics.ticketon.app.dao.coherence.TicketCacheStore)]", State=Running}
2010-02-11 09:26:52.225/511.459 Oracle Coherence GE 3.5.2/463 <Error> (thread=Termination Thread, member=2): Write-behind thread timed out; stopping the cache service
2010-02-11 09:26:52.226/511.460 Oracle Coherence GE 3.5.2/463 <D5> (thread=DistributedCache:TicketonCache, member=2): Service TicketonCache left the cluster
INFO 09:26:52,227 [http--80-22$27432016 DaoCoherenceImpl] - PROFILE_doCreatetickets putAll 200 tickets time 3444 time per 10 objects 172
INFO 09:26:52,227 [http--80-22$27432016 DaoCoherenceImpl] - PROFILE event and 1000 tickets ctreated time 9668
Broadcast Message from root (msglog) on ip-10-226-137-172 Thu Feb 11 09:57:18...ets putAll 200 tickets time 3365 time per 10 objects 168
2010-02-11 09:26:52.228/511.462 Oracle Coherence GE 3.5.2/463 <Info> (thread=httTHE SYSTEM ip-10-226-137-172 IS BEING SHUT DOWN NOW ! ! !et
Log off now or risk your files being damagedence GE 3.5.2/463 <Info> (thread=http--80-27$25787595, member=2): Restarting Service: TicketonCache
INFO 09:26:52,229 [http--80-20$15974570 DaoCoherenceImpl] - PROFILE_doCreatetickets putAll 200 tickets time 3447 time per 10 objects 172
INFO 09:26:52,289 [http--80-22$26935588 BackingBeanSuper] - request HttpRequest[22]
[09:26:53.446] {http--80-35$24027494} java.lang.RuntimeException: Failed to start Service "TicketonCache" (ServiceState=SERVICE_STOPPED)
[09:26:53.446] {http--80-35$24027494} at com.tangosol.coherence.component.util.daemon.queueProcessor.Service.waitAcceptingClients(Service.CDB:12)
Resume: coherence crashes in case far from fatal.
Questions
1. May i limit the size of a batch passed to cachestore?
2. Is it possible to configure the timeout "(due to hard timeout 1924ms ago)"
3. Is it possible to handle like this some way to prevent self killing of coherence cluster.Thank you Mark you are vary helpfull
Did you mean that (lower) by "bundle strategy"?
<cachestore-scheme>
<class-scheme>
<class-name>com.griddynamics.ticketon.app.dao.coherence.TicketCacheStore</class-name>
</class-scheme>
<operation-bundling>
<bundle-config>
<operation-name>store</operation-name>
<preferred-size>5000</preferred-size>
<auto-adjust>true</auto-adjust>
</bundle-config>
</operation-bundling>
</cachestore-scheme>
And if yes is it looks sense?
I mean by this, "send records to TicketCacheStore by 5000 per call " am i right?
I dropped delay to 10s and set factor to 0.5
Not coherece send me 5-20k records and cachestore handle whis successfuly.
But! By diferent means it may work longer sometimes, some lock in database for instance.
I want to find durable solution for the case, not only lower a chance i meet one.
Issuing heartbeat from cachestore looks best for me now.
I find that default guardian timeout is 65s and it is not looks as good idea to make it higher. -
Switching from write through to write behind automatically
Hi,
We are considering a Coherence solution to protect a customer facing application from outages due to database failures. This is for a financial company and the monetary value of each transaction is large and we want to provide 100% guarantee against data loss while not incurring any outages. We want to provide a write-through persistence to the database through Coherence which can switch to a write-behind automatically at runtime if the database persistence fails. Is this doable automatically and would it solve the problem I am trying to solve without losing any inflight transactions? Are there any real customer cases that were successful in achieving this using Coherence?
Thanks
Sairam
Edited by: SKR on Feb 16, 2012 3:14 PM
Edited by: SKR on Feb 16, 2012 3:15 PMSKR wrote:
Jonathan.Knight wrote:
Hi Sairam
I know you can change the write-delay in JMX for a cache using write-behind but I pretty certauin you cannot make a write-through cache suddenly become a write-behind cache.
I'm not sure why you think changing from write-through to write-behind will allow you to guarantee 100% no data loss - do you mean no loss of updates to the DB or no loss of data in the cache cluster? There are certainly scenarios that can occur where you can loose data from either the cluster or the DB that write-through or write-behind will not save you from. Presumably you want to use write-behind to allow for the DB to go down, although you will still need to configure Coherence to properly retry failed write-behind calls CacheStore behaviour on failure. What happens to your data if you are using write-behind and you loose a partition from you cluster (i.e. you loose a physical machine or two or more JVMs in a short space of time) - you have data loss - you cannot guarantee against this you can only mitigate it and have a recovery policy/procedure.
JKJK,
Thanks for your reply. I must have explained the scenario better. What we are trying to do is to have our transactions commit to the database synchronously using write-through, so that during normal operation, the data will be committed, persisted and durable in the database. But our RW database becomes a single point of failure and if some problem occurs to the database during the peak load time, we run the risk of an outage till we fix the database problem or failover to the standby (We don't have RAC architecture or automatic failover and the manual switchover takes about 10 - 15 mins minimum). We want to avoid this by providing a cache-only operation mode during such a failure, where the customers can continue to transact and the writes will get queued in the cache. I do understand that losing both the database and the cache or losing the primary and the backup in the cache would result in a data loss. But I am assuming such a dual failure is rare.
We do not want to run write-behind all the time but only during the database failure window. From what you mentioned, it seems the runtime switching from write-through to write-behind is not available as an option.
SairamHi Sairam,
I would suggest that you configure write-behind to have a fairly short write-delay, and you only return a confirmation to the client
- either after the write-behind succeeded (you can use a backing map listener to listen for the removal of the decoration which meant that the entry was dirty)
- or if the database went down (noticeable from the failure), then it is up to you whether you send a confirmation which also mentions that it is not persisted to disk yet, or not at all
Best regards,
Robert -
Write-Behind Caching and Old Values
Is there a way to access the old value cached in the write-behind cache for the same key from the CacheStore's store() or storeAll() method?
I have a business POJO with three parts: partA, > partB, partC inside. Each of these three parts is
> persisted by a separate SQL. So, every time I persist
> my POJO, up to 3 SQLs may be executed.
I understand.
> When a change happens in my POJO, it goes onto the
> write-behind queue. In my CacheStore.store() or
> CacheStore.storeAll() I would like to be able to make
> an intelligent decision about which of the three
> parts: partA, partB or partC has actually changed and
> only run the SQL updates for the changed parts. This
> would allow me to avoid massive amounts of
> unnecessary SQL updates for the parts that did not
> change.
Right. Keep in mind that there are two conditions that you must be aware of:
1) Multiple updates could have occurred to the object, meaning that the database update would have to "roll up" the results of multiple changes to the object.
2) Some or all of the updates could have already occurred to the database. This may be a little trickier to understand, but it reflects the possible machine failure conditions that occurred while a write-behind was in progress.
Although the latter are unlikely, they should be accounted for, and of course they are harder to test for with certainty. As a result, the updates to the information (the CacheStore implementation) must be built in an "idempotent" manner, i.e. allowing it to be executed more than once with no additional side-effects.
> If I had access to the POJO stored under the same key
> before the new value was put in cache, I could use
> equals() on each of the three parts to find out
> exactly which one of them changed.
While this is true, you would need to compare the "known previous database state" version, not just the "old" version.
> Of course, if this functionality is not available, I
> would have to create dirty flags for each of the
> three POJO parts. But I can't really clear my POJO's
> flags and recache the POJO from within the store() or
> storeAll(), right?
Yes, but remember that those flags are "could be dirty" flags, because of the above failure modes that I described.
Peace,
Cameron Purdy
Tangosol Coherence: The Java Data Grid -
Hi,
We are trying to test the speed of the write behind mechanism and we would be interested to know how other coherence users handle, for example, writing 1 million rows into the database.
At the moment, using jdbc batch inserts we can write approximately 30000 rows per minute, which means it would take about 30 minutes to save 1 million rows. Are there any other methods that other coherence user's use that can improve on this?
Many thanks,user738616 wrote:
Hi,
This has nothing to do with Coherence as the implementation of CacheStore is outside of Coherence. Apart from JDBC Batch, you should try using PLSQL Bulk binds for such numbers.
Hope this helps!
Cheers,
NJHi NJ,
we actually measured PLSQL bulk binds against plain SQL (both with JDBC)... for anything which can be translated to plain inserts/updates, plain SQL is way faster (more than 10x).
You can only win with bulk binds when that statement which you send down actually does more complex logic and multiple statements so you actually win with optimizing away the roundtrips, too.
Best regards,
Robert -
Write-behind cache not removing entries after upgrade to 3.2
We recently upgraded tangosol.jar and coherence.jar from version 3.0 to version 3.2. After the upgrade, our write-behind caches began consuming all available memory and crashing the JVMs because the entries were not being removed from the cache after being written to the database. We rolled back to the 3.0 jars without making any other modifications and the caches behave as expected. We'd really like to move to 3.2 for the improved network fault tolerance, but we need to resolve this issue first.
What changes were made in 3.2 with respect to write-behind caches that might cause this issue? I've reviewed our configuration and our code and can't find anything unusual, but I'm not sure what I should be looking for.
Any ideas?I've opened an SR, but I haven't heard back. In the meantime, I've continued digging and I've noticed something strange - in the store() method of our backing map implementation, we take the entry that we just persisted and remove it from the backing map.
In my small-scale local tests, the size of the map is 1 when we enter store() and is 0 when we leave, as expected. If we process another entry using the 3.0 jars, it's again 1 and then 0. However, it gets more interesting with the 3.2 jars - the size of the map is 1 when we enter store() the first time and 0 when we leave, but if we process another entry, the size is 2 when we enter and 1 when we leave. This pattern continues such that both values increase by 1 every time we process an entry.
This would imply that we're either removing the entries incorrectly, or they're somehow being reinserted into the map.
Any ideas?
Here's the body of our method (with a bunch of sysouts added to the normal logging because this app won't run correctly under a debugger):
* Store the specified value under the specific key in the underlying
* store, then remove the specific key from the internal map and hence
* the cache itself. This method is intended to support both key/value
* creation and value update for a specific key.
* @param oKey key to store the value under
* @param oValue value to be stored
* @throws UnsupportedOperationException if this implementation or the
* underlying store is read-only
public void store(Object oKey, Object oValue)
RemoveOnStoreRWBackingMap mapBacking = RemoveOnStoreRWBackingMap.this;
System.out.println("map storing " + oKey);
System.out.println("Size before = " + mapBacking.entrySet().size());
Iterator entries = mapBacking.entrySet().iterator();
while (entries.hasNext()) {
System.out.println("entry = " + entries.next());
String storeClassName = getCacheStore().getClass().getName();
Logger log = Logger.getLogger(storeClassName);
log.debug(storeClassName + ": In store method. Storing " + oKey);
long cFailuresBefore = getStoreFailures();
log.debug(storeClassName + ": failures before=" + cFailuresBefore);
super.store(oKey, oValue);
long cFailuresAfter = getStoreFailures();
log.debug(storeClassName + ": failures afer=" + cFailuresAfter);
if (cFailuresBefore == cFailuresAfter) {
log.debug(storeClassName + ": About to remove");
mapBacking = RemoveOnStoreRWBackingMap.this;
Converter converter = mapBacking.getContext().getKeyToInternalConverter();
System.out.println("removed " + mapBacking.remove(converter.convert(oKey)));
// System.out.println("removed " + mapBacking.getInternalCache().remove(converter.convert(oKey)));
log.debug(storeClassName + ": Removed");
Converter converter = RemoveOnStoreRWBackingMap.this.getContext().getKeyFromInternalConverter();
System.out.println("Size after = " + mapBacking.entrySet().size());
} -
Hi,
Suddenly I got this error in SCVMM 2012-R2 Roll-up 1:
When working with User-Roles (create/update) or assigning a Cloud :
"VMM encountered a critical exception and created an exception report....
search user forums for well-known failure root causes for self-help" (how sweet)... (if it's "well known", why not coding the exception handling correctly?)
The relevant part of the report might be this:
"SCVMM Version=3.2.7620.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=3.2.7620.0
Executable Name=vmmservice.exe
Executable Version=3.2.7510.0
Base Exception Target Site=140717670746840
Base Exception Assembly name=System.Data.dll
Base Exception Method Name=System.Data.SqlClient.SqlConnection.OnError
Exception Message=Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again."
(side question: what does this mean: "Ensure that the SQL Server is ... configured correctly"?
I can say that :
SQL is configured by the book, that all services are running (did a reboot of VMM server too) and that all other VMM functions work OK. I don't believe that SQL is only used for user-roles...
Acting as Domain admin and VMM admin.
All updates are installed.
Please find the report @the and and a screen shot attached.
Thanks for any help.
Report.txt:
------------------- Error Report -------------------
Error report created 03.04.2014 15:07:56
CLR is not terminating
--------------- Bucketing Parameters ---------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=3.2.7620.0
P3(assemblyName)=Utils.dll
P4(assemblyVer)=3.2.7620.0
P5(methodName)=Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery
P6(exceptionType)=Microsoft.VirtualManager.DB.CarmineSqlException
P7(callstackHash)=4c11
SCVMM Version=3.2.7620.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=3.2.7620.0
Executable Name=vmmservice.exe
Executable Version=3.2.7510.0
Base Exception Target Site=140717670746840
Base Exception Assembly name=System.Data.dll
Base Exception Method Name=System.Data.SqlClient.SqlConnection.OnError
Exception Message=Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again.
EIP=0x00007ffb74c75a88
Build bit-size=64
------------ exceptionObject.ToString() ------------
Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again. ---> System.Data.SqlClient.SqlException: Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
--- End of inner exception stack trace ---
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
*** Carmine error was: DatabaseFailure (2605); SQLServer; 8144
[s#5cf2] ExecuteNonQuery()
[s#5c38] Task`1.SubtaskRun(this: (Task`1#b), TaskID: (guid) 0e1c3e3d-76de-4d8b-bfc2-cbcc400fadf4)
Full call stack from when the exception was thrown: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at Microsoft.VirtualManager.DB.CarmineSqlException..ctor(SqlException sqlException)
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
--- SqlException details -----------------
System.Data.SqlClient.SqlException (0x80131904): Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
ClientConnectionId:b85c83f3-e87d-4ec4-af12-41b4dd6ad8cb
Error = 8144
Index #0
Source: .Net SqlClient Data Provider
Number: 8144
State: 2
Class: 16
Server: localhost\SCVMM
Message: Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
Procedure: prc_RBS_UserRoleSharedObjectRelation_Insert
Line: 0
--- Caller StackTrace -----------------
FileName:; Method:ExecuteNonQuery(); lineNo:0; ilOffset:178.
FileName:; Method:<AddObjectSharingData>b__14(); lineNo:0; ilOffset:12.
FileName:; Method:<HandleInsertErrors>b__3(); lineNo:0; ilOffset:11.
FileName:; Method:HandleInsertErrors(); lineNo:0; ilOffset:6.
FileName:; Method:AddObjectSharingData(); lineNo:0; ilOffset:312.
FileName:; Method:AddSharingData(); lineNo:0; ilOffset:23.
FileName:; Method:AddResourceSharing(); lineNo:0; ilOffset:464.
FileName:; Method:RunSharingSubTask(); lineNo:0; ilOffset:49.
FileName:; Method:RunSubtask(); lineNo:0; ilOffset:23.
FileName:; Method:Run(); lineNo:0; ilOffset:354.
FileName:; Method:RunNewAndSetUserRoleSubtasks(); lineNo:0; ilOffset:166.
FileName:; Method:RunSubtask(); lineNo:0; ilOffset:140.
FileName:; Method:Run(); lineNo:0; ilOffset:354.
FileName:; Method:SubtaskRun(); lineNo:0; ilOffset:221.
FileName:; Method:RunInternal(); lineNo:0; ilOffset:112.
FileName:; Method:Run(); lineNo:0; ilOffset:4.
FileName:; Method:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem(); lineNo:0; ilOffset:0.
FileName:; Method:Dispatch(); lineNo:0; ilOffset:162.
-------- exception.InnerException.ToString() -------
System.Data.SqlClient.SqlException (0x80131904): Procedure or function prc_RBS_UserRoleSharedObjectRelation_Insert has too many arguments specified.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
ClientConnectionId:b85c83f3-e87d-4ec4-af12-41b4dd6ad8cb
--------------- exception.StackTrace ---------------
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.<>c__DisplayClass15.<AddObjectSharingData>b__14()
at Microsoft.VirtualManager.Engine.DbAccessHelper.<>c__DisplayClass4.<HandleInsertErrors>b__3()
at Microsoft.VirtualManager.Engine.DbAccessHelper.HandleInsertErrors[_RetTy](DbAccessDelegate`1 func, ErrorInfo duplicateErrorInfo)
at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.AddObjectSharingData(SqlContext ctx, ITaskContext taskCtx, Guid objectId, CarmineObjectType objectType, AccessControlData accessData)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddSharingData(SqlContext ctx, ITaskContext taskContext, LockableObject resource, AccessControlData data)
at Microsoft.VirtualManager.DB.DelegatedAdmin.ResourceSharingHelper.AddResourceSharing(SqlContext ctx, ITaskContext taskCtx, LockableObject resource, List`1 destinationRoles, UserOrGroup destinationUser)
at Microsoft.VirtualManager.Engine.AuthorizationManager.GrantResourceTask.RunSharingSubTask()
at Microsoft.VirtualManager.Engine.AuthorizationManager.ResourceSharingTaskBase.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.AuthorizationManager.UserRoleTaskHelper.RunNewAndSetUserRoleSubtasks(ITaskContext taskContext, List`1 queuedSubtasks, UserRoleData userRoleData)
at Microsoft.VirtualManager.Engine.AuthorizationManager.SetUserRoleSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
------------- StackTrace from handler --------------
This is the call stack from where the exception was caught, not where it was thrown.
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.WriteReportTextFile(TextWriter reportFile)
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonExceptionReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonCenter.ReportException(Exception e, WERReportOptions options, String& localReportPath)
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
-------------------- Assemblies --------------------
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Module=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Version=4.0.30319.34011
BuildType=retail
Product=Microsoft® .NET Framework
VMMService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Version=4.0.30319.34003
BuildType=retail
Product=Microsoft® .NET Framework
TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NativeMethods, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Common, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.IndigoAccessLayer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Skuhelper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Errors, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Remoting, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.Adhc.Operations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.TaskRepository, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ImgLibEngine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VmmHelperHost, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VirtualizationInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NetworkServiceInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ClusterUtil, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VMWareImplementation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManagerTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Backup, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.BitBos, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Version=6.3.9600.16394
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
WsManWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
SqmWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Deployment, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement.ResourceModel, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ImgLibOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.CustomProperties, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.VmOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.MomDal, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.PxeServer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.P2VCommon, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
PatchExtractor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Engine.ConfigurationProviders, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GatewayInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Version=6.3.9600.16384
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
Microsoft.CapacityManager.Modeling.Store.ModelLibrary, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CustomPropertyTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.UMOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Tasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ServiceOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GoalState, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CloudService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
WSManAutomation, Version=3.2.7510.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
wmiWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
SMDiagnostics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
DB.DelegatedAdmin, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
Version=3.2.7620.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
DB.TieredPerfCounters, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.PhysicalMachine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
Version=3.2.7515.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.UpdateManagement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.RunAs, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.DB.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.IdentityModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.IdentityModel\v4.0_4.0.0.0__b77a5c561934e089\System.IdentityModel.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
--------- Extra Data for Watson Report -------------
Error Reporting Enabled=True
*** Extra Data ***
Process ID = 1500 (0x05dc)
Managed Thread ID = 25
Native Thread ID = 1260 (0x04ec)
Thomas.I (quite honestly) am one of those folks that generally do not read the KB articles associated with a patch or UR or SP - as you don't expect details like have been put into this particular one.
But as Kristian pointed out - within that KB article is the SQL script that modifies / updates this SQL Stored Procedure.
http://blogs.technet.com/b/scvmm/archive/2014/01/29/how-to-update-scvmm-2012-r2-to-update-rollup-1.aspx
Needless to say, the feedback was given to MSFT that folks would overlook that this SQL script needed to be run. So we are just trying to help out.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
TTL specified in put operation doesn't always work when using write-behind
I'm using a distributed cache with a write-behind cache store (see the config below). I found that when I do something like myCache.put(key, value, ttl), the entry survives the specified ttl. I tried doing the same with a distributed cache with a write-through cachestore and there everything does happen correctly.
Is this sort of operation not permitted in caches containing a write-behind cachestore? If not wouldn't it be better to throw an UnsupportedOperationException.
I created a small test to simulate this. I added values to the cache with a TTL of 1 to 10 seconds and found that the 10 second entries stayed in the cache.
Configuration used:
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>TTL_TEST</cache-name>
<scheme-name>testScheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>testScheme</scheme-name>
<service-name>testService</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<local-scheme>
<service-name>testBackLocalService</service-name>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<scheme-name>testBackStore</scheme-name>
<class-name>TTLTestServer$TestCacheStore</class-name>
</class-scheme>
</cachestore-scheme>
<write-delay>3s</write-delay>
</read-write-backing-map-scheme>
</backing-map-scheme>
<local-storage>true</local-storage>
<autostart>true</autostart>
</distributed-scheme>
</caching-schemes>
</cache-config>Code of test:
import java.util.Collection;
import java.util.List;
import java.util.Map;
import java.util.concurrent.Callable;
import java.util.concurrent.ExecutionException;
import java.util.concurrent.ExecutorService;
import java.util.concurrent.Executors;
import java.util.concurrent.Future;
import org.joda.time.DateTime;
import org.joda.time.Duration;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
import org.springframework.util.StopWatch;
import org.testng.annotations.BeforeClass;
import org.testng.annotations.Test;
import com.google.common.collect.Lists;
import com.tangosol.net.CacheFactory;
import com.tangosol.net.NamedCache;
import com.tangosol.net.cache.CacheStore;
@Test
public class TTLTestServer
private static final int RETRIES = 5;
private static final Logger logger = LoggerFactory.getLogger( TTLTestServer.class );
private NamedCache m_cache;
* List of Time-To-Lives in seconds to check
private final List<Integer> m_listOfTTLs = Lists.newArrayList(1, 3, 5, 10);
* Test is done in separate threads to speed up the test
private final ExecutorService m_executorService = Executors.newCachedThreadPool();
@BeforeClass
public void setup()
logger.info("Getting the cache");
m_cache = CacheFactory.getCache("TTL_TEST");
public static class TestCacheStore implements CacheStore
public void erase(Object arg0)
public void eraseAll(Collection arg0)
public void store(Object arg0, Object arg1)
public void storeAll(Map arg0)
public Object load(Object arg0)
{return null;}
public Map loadAll(Collection arg0)
{return null;}
public void testTTL() throws InterruptedException, ExecutionException
logger.info("Starting TTL test");
List<Future<StopWatch>> futures = Lists.newArrayList();
for (final Integer ttl : m_listOfTTLs)
futures.add(m_executorService.submit(new Callable()
public Object call() throws Exception
StopWatch stopWatch= new StopWatch("TTL=" + ttl);
for (int retry = 0; retry < RETRIES; retry++)
logger.info("Adding a value in cache for TTL={} in try={}", ttl, retry+1);
stopWatch.start("Retry="+retry);
m_cache.put(ttl, null, ttl*1000);
waitUntilNotInCacheAnymore(ttl, retry);
stopWatch.stop();
return stopWatch;
private void waitUntilNotInCacheAnymore(final Integer ttl, final int currentTry) throws InterruptedException
DateTime startTime = new DateTime();
long maxMillisToWait = ttl*2*1000; //wait max 2 times the time of the ttl
while(m_cache.containsKey(ttl) )
Duration timeTaken = new Duration(startTime, new DateTime());
if(timeTaken.getMillis() > maxMillisToWait)
throw new RuntimeException("Already waiting " + timeTaken + " for ttl=" + ttl + " and retry=" + currentTry);
Thread.sleep(1000);
logger.info("Waiting until all futures are finished");
m_executorService.shutdown();
logger.info("Getting results from futures");
for (Future<StopWatch> future : futures)
StopWatch sw = future.get();
logger.info(sw.prettyPrint());
}Failure message:
FAILED: testTTL
java.util.concurrent.ExecutionException: java.lang.RuntimeException: Already waiting PT20.031S for ttl=10 and retry=0
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at TTLTestServer.testTTL(TTLTestServer.java:159)
Caused by: java.lang.RuntimeException: Already waiting PT20.031S for ttl=10 and retry=0
at TTLTestServer$1.waitUntilNotInCacheAnymore(TTLTestServer.java:139)
at TTLTestServer$1.call(TTLTestServer.java:122)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)I'm using Coherence 3.4.2.
Best regards
JanHi, still no luck. However, I noticed that setting the write-delay value of the write-behind store to 0s or 1s, solved the problem. It only starts to given me "the node has already been removed" excpetions once the write-delay value is 2s or higher.
You can find the coherence-cache-config.xml below:
<?xml version="1.0"?>
<!DOCTYPE cache-config SYSTEM "cache-config.dtd">
<cache-config>
<caching-scheme-mapping>
<cache-mapping>
<cache-name>TTL_TEST</cache-name>
<scheme-name>testScheme</scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<distributed-scheme>
<scheme-name>testScheme</scheme-name>
<service-name>testService</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<local-scheme>
<service-name>testBackLocalService</service-name>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<scheme-name>testBackStore</scheme-name>
<class-name>TTLTestServer$TestCacheStore</class-name>
</class-scheme>
</cachestore-scheme>
<write-delay>2s</write-delay>
</read-write-backing-map-scheme>
</backing-map-scheme>
<local-storage>true</local-storage>
<autostart>true</autostart>
</distributed-scheme>
</caching-schemes>
</cache-config>You can find the test program below:
import java.util.ArrayList;
import java.util.Collection;
import java.util.List;
import java.util.Map;
import org.joda.time.DateTime;
import org.joda.time.Duration;
import org.springframework.util.StopWatch;
import com.tangosol.net.CacheFactory;
import com.tangosol.net.NamedCache;
import com.tangosol.net.cache.CacheStore;
public class TTLTestServer
private static final int RETRIES = 5;
private NamedCache m_cache;
* List of Time-To-Lives in seconds to check
private final List<Integer> m_listOfTTLs = new ArrayList<Integer>();
* @param args
* @throws Exception
public static void main( String[] args ) throws Exception
new TTLTestServer().test();
* Empty CacheStore
* @author jbe
public static class TestCacheStore implements CacheStore
public void erase(Object arg0)
@SuppressWarnings ( "unchecked" )
public void eraseAll(Collection arg0)
public void store(Object arg0, Object arg1)
@SuppressWarnings ( "unchecked" )
public void storeAll(Map arg0)
public Object load(Object arg0)
{return null;}
@SuppressWarnings ( "unchecked" )
public Map loadAll(Collection arg0)
{return null;}
* Sets up and executes the test setting values in a cache with a given time-to-live value and waiting for the value to disappear.
* @throws Exception
private void test() throws Exception
System.out.println(new DateTime() + " - Setting up TTL test");
m_cache = CacheFactory.getCache("TTL_TEST");
m_listOfTTLs.add( 1 );
m_listOfTTLs.add( 3 );
m_listOfTTLs.add( 5 );
m_listOfTTLs.add( 10);
System.out.println(new DateTime() + " - Starting TTL test");
for (final Integer ttl : m_listOfTTLs)
StopWatch sw = doTest(ttl);
System.out.println(sw.prettyPrint());
* Adds a value to the cache with the time-to-live as given by the ttl parameter and waits until it's removed from the cache.
* Repeats this {@link #RETRIES} times
* @param ttl
* @return
* @throws Exception
private StopWatch doTest(Integer ttl) throws Exception
StopWatch stopWatch= new StopWatch("TTL=" + ttl);
for (int retry = 0; retry < RETRIES; retry++)
System.out.println(new DateTime() + " - Adding a value in cache for TTL=" + ttl + " in try= " + (retry+1));
stopWatch.start("Retry="+retry);
m_cache.put(ttl, null, ttl*1000);
waitUntilNotInCacheAnymore(ttl, retry);
stopWatch.stop();
return stopWatch;
* Wait until the value for the given ttl is not in the cache anymore
* @param ttl
* @param currentTry
* @throws InterruptedException
private void waitUntilNotInCacheAnymore(final Integer ttl, final int currentTry) throws InterruptedException
DateTime startTime = new DateTime();
long maxMillisToWait = ttl*2*1000; //wait max 2 times the time of the ttl
while(m_cache.containsKey(ttl) )
Duration timeTaken = new Duration(startTime, new DateTime());
if(timeTaken.getMillis() > maxMillisToWait)
throw new RuntimeException("Already waiting " + timeTaken + " for ttl=" + ttl + " and retry=" + currentTry);
Thread.sleep(1000);
}You can find the output below:
2009-12-03T11:50:04.584+01:00 - Setting up TTL test
2009-12-03 11:50:04.803/0.250 Oracle Coherence 3.5.2/463p2 <Info> (thread=main, member=n/a): Loaded operational configuration from resource "jar:file:/C:/Temp/coherence3.5.2/coherence-java-v3.5.2b463-p1_2/coherence/lib/coherence.jar!/tangosol-coherence.xml"
2009-12-03 11:50:04.803/0.250 Oracle Coherence 3.5.2/463p2 <Info> (thread=main, member=n/a): Loaded operational overrides from resource "jar:file:/C:/Temp/coherence3.5.2/coherence-java-v3.5.2b463-p1_2/coherence/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-12-03 11:50:04.803/0.250 Oracle Coherence 3.5.2/463p2 <D5> (thread=main, member=n/a): Optional configuration override "/tangosol-coherence-override.xml" is not specified
2009-12-03 11:50:04.803/0.250 Oracle Coherence 3.5.2/463p2 <D5> (thread=main, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
Oracle Coherence Version 3.5.2/463p2
Grid Edition: Development mode
Copyright (c) 2000, 2009, Oracle and/or its affiliates. All rights reserved.
2009-12-03 11:50:04.943/0.390 Oracle Coherence GE 3.5.2/463p2 <Info> (thread=main, member=n/a): Loaded cache configuration from "file:/C:/jb/workspace3.5/TTLTest/target/classes/coherence-cache-config.xml"
2009-12-03 11:50:05.318/0.765 Oracle Coherence GE 3.5.2/463p2 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2009-12-03 11:50:08.568/4.015 Oracle Coherence GE 3.5.2/463p2 <Info> (thread=Cluster, member=n/a): Created a new cluster "cluster:0xD3FB" with Member(Id=1, Timestamp=2009-12-03 11:50:05.193, Address=172.16.44.32:8088, MachineId=36896, Location=process:11848, Role=TTLTestServerTTLTestServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=2) UID=0xAC102C20000001255429380990201F98
2009-12-03 11:50:08.584/4.031 Oracle Coherence GE 3.5.2/463p2 <D5> (thread=Invocation:Management, member=1): Service Management joined the cluster with senior service member 1
2009-12-03 11:50:08.756/4.203 Oracle Coherence GE 3.5.2/463p2 <D5> (thread=DistributedCache:testService, member=1): Service testService joined the cluster with senior service member 1
2009-12-03T11:50:08.803+01:00 - Starting TTL test
2009-12-03T11:50:08.818+01:00 - Adding a value in cache for TTL=1 in try= 1
2009-12-03T11:50:09.818+01:00 - Adding a value in cache for TTL=1 in try= 2
Exception in thread "main" (Wrapped: Failed request execution for testService service on Member(Id=1, Timestamp=2009-12-03 11:50:05.193, Address=172.16.44.32:8088, MachineId=36896, Location=process:11848, Role=TTLTestServerTTLTestServer)) java.lang.IllegalStateException: the node has already been removed
at com.tangosol.util.Base.ensureRuntimeException(Base.java:293)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.tagException(Grid.CDB:36)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onContainsKeyRequest(DistributedCache.CDB:41)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache$ContainsKeyRequest.run(DistributedCache.CDB:1)
at com.tangosol.coherence.component.net.message.requestMessage.DistributedCacheKeyRequest.onReceived(DistributedCacheKeyRequest.CDB:12)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onMessage(Grid.CDB:9)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.Grid.onNotify(Grid.CDB:136)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onNotify(DistributedCache.CDB:3)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:42)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: the node has already been removed
at com.tangosol.util.AbstractSparseArray$Crawler.remove(AbstractSparseArray.java:1274)
at com.tangosol.net.cache.OldCache.evict(OldCache.java:580)
at com.tangosol.net.cache.OldCache.containsKey(OldCache.java:171)
at com.tangosol.net.cache.ReadWriteBackingMap.containsKey(ReadWriteBackingMap.java:597)
at com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.DistributedCache.onContainsKeyRequest(DistributedCache.CDB:25)
... 7 more
2009-12-03 11:50:10.834/6.281 Oracle Coherence GE 3.5.2/463p2 <D4> (thread=ShutdownHook, member=1): ShutdownHook: stopping cluster node
2009-12-03 11:50:10.834/6.281 Oracle Coherence GE 3.5.2/463p2 <D5> (thread=Cluster, member=1): Service Cluster left the clusterBest regards
Jan -
General Database failure - Urgent assistance needed
I've have the following error report:
------------------- Error Report -------------------
Error report created 1/1/2014 10:15:52 PM
CLR is not terminating
--------------- Bucketing Parameters ---------------
EventType=VMM20
P1(appName)=vmmservice.exe
P2(appVersion)=3.2.7510.0
P3(assemblyName)=Utils.dll
P4(assemblyVer)=3.2.7510.0
P5(methodName)=Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery
P6(exceptionType)=Microsoft.VirtualManager.DB.CarmineSqlException
P7(callstackHash)=e796
SCVMM Version=3.2.7510.0
SCVMM flavor=C-buddy-RTL-AMD64
Default Assembly Version=3.2.7510.0
Executable Name=vmmservice.exe
Executable Version=3.2.7510.0
Base Exception Target Site=140710978931416
Base Exception Assembly name=System.Data.dll
Base Exception Method Name=System.Data.SqlClient.SqlConnection.OnError
Exception Message=Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again.
EIP=0x00007ff9e45bab78
Build bit-size=64
------------ exceptionObject.ToString() ------------
Microsoft.VirtualManager.DB.CarmineSqlException: Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again. ---> System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "fk__ADHC_HostDisk__ADHC_ClusterDisk". The conflict
occurred
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
--- End of inner exception stack trace ---
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.Adhc.HostDisk.InsertIntoDB(HostDiskData data, SqlContext ctx)
at Microsoft.VirtualManager.DB.Adhc.HostDisk.CreateInstance(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.DB.Adhc.Host.CreateHostDisk(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.<>c__DisplayClassb.<UpdateDiskAndVolumeInfo>b__6(HostDiskData d, SqlContext ctx)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDbObjects[TObj,TObjData](List`1 existing, List`1 fresh, ObjectDataComparer`2 isEqual, NewObjectCreator`2 createNew, SqlContext ctx, Guid taskID, Boolean deleteNonExisting, Boolean
ignoreDeleteErrors, List`1 skipExistingOnDelete)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDiskAndVolumeInfo(Host host, List`1 existingDisks, List`1 refreshedDisks, List`1 existingVolumes, List`1 refreshedVolumes, Dictionary`2 volumeToDiskMap, CarmineObjectType serverType,
Guid serverId, Nullable`1 hostGroupId, Guid taskID, SqlContext context, Boolean deleteNonExisting, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDatabase()
at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.UpdateAllInformation(Host host, HostUpdateInformation hostUpdateInfo, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.UpdateDb(HostClusterProperties refresher, HostCluster cluster, List`1 hosts, Dictionary`2 lockedHosts, ClusterUpdateInformation clusterInfo, List`1 hostInfos, Guid taskID, ITaskContext
taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.RefreshHostClusterSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
*** Carmine error was: DatabaseFailure (2605); SQLServer; 547
[s#10003db] ExecuteNonQuery()
[s#fff15e] Task`1.SubtaskRun(this: (Task`1#12), TaskID: (guid) a1c63c5c-1527-4729-8012-6559a196b7a7)
Full call stack from when the exception was thrown: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)
at System.Environment.get_StackTrace()
at Microsoft.VirtualManager.DB.CarmineSqlException..ctor(SqlException sqlException)
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.Adhc.HostDisk.InsertIntoDB(HostDiskData data, SqlContext ctx)
at Microsoft.VirtualManager.DB.Adhc.HostDisk.CreateInstance(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.DB.Adhc.Host.CreateHostDisk(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.<>c__DisplayClassb.<UpdateDiskAndVolumeInfo>b__6(HostDiskData d, SqlContext ctx)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDbObjects[TObj,TObjData](List`1 existing, List`1 fresh, ObjectDataComparer`2 isEqual, NewObjectCreator`2 createNew, SqlContext ctx, Guid taskID, Boolean deleteNonExisting, Boolean
ignoreDeleteErrors, List`1 skipExistingOnDelete)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDiskAndVolumeInfo(Host host, List`1 existingDisks, List`1 refreshedDisks, List`1 existingVolumes, List`1 refreshedVolumes, Dictionary`2 volumeToDiskMap, CarmineObjectType serverType,
Guid serverId, Nullable`1 hostGroupId, Guid taskID, SqlContext context, Boolean deleteNonExisting, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDatabase()
at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.UpdateAllInformation(Host host, HostUpdateInformation hostUpdateInfo, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.UpdateDb(HostClusterProperties refresher, HostCluster cluster, List`1 hosts, Dictionary`2 lockedHosts, ClusterUpdateInformation clusterInfo, List`1 hostInfos, Guid taskID, ITaskContext
taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.RefreshHostClusterSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
--- SqlException details -----------------
System.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "fk__ADHC_HostDisk__ADHC_ClusterDisk". The conflict occurred
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
ClientConnectionId:0fca7b02-93ca-4a31-b609-0b6244178b6a
Error = 547
Index #0
Source: .Net SqlClient Data Provider
Number: 547
State: 0
Class: 16
Server: VMM-SRV
Message: The INSERT statement conflicted with the FOREIGN KEY constraint "fk__ADHC_HostDisk__ADHC_ClusterDisk". The conflict occurred
Procedure: prc_ADHC_HostDisk_Insert
Line: 39
Index #1
Source: .Net SqlClient Data Provider
Number: 3621
State: 0
Class: 0
Server: VMM-SRV
Message: The statement has been terminated.
Procedure: prc_ADHC_HostDisk_Insert
Line: 39
--- Caller StackTrace -----------------
FileName:; Method:ExecuteNonQuery(); lineNo:0; ilOffset:178.
FileName:; Method:InsertIntoDB(); lineNo:0; ilOffset:740.
FileName:; Method:CreateInstance(); lineNo:0; ilOffset:23.
FileName:; Method:CreateHostDisk(); lineNo:0; ilOffset:19.
FileName:; Method:<UpdateDiskAndVolumeInfo>b__6(); lineNo:0; ilOffset:50.
FileName:; Method:UpdateDbObjects(); lineNo:0; ilOffset:374.
FileName:; Method:UpdateDiskAndVolumeInfo(); lineNo:0; ilOffset:769.
FileName:; Method:UpdateDatabase(); lineNo:0; ilOffset:728.
FileName:; Method:UpdateAllInformation(); lineNo:0; ilOffset:108.
FileName:; Method:UpdateDb(); lineNo:0; ilOffset:539.
FileName:; Method:RefreshLockedCluster(); lineNo:0; ilOffset:419.
FileName:; Method:RefreshLockedCluster(); lineNo:0; ilOffset:440.
FileName:; Method:RunSubtask(); lineNo:0; ilOffset:400.
FileName:; Method:Run(); lineNo:0; ilOffset:354.
FileName:; Method:SubtaskRun(); lineNo:0; ilOffset:221.
FileName:; Method:RunInternal(); lineNo:0; ilOffset:112.
FileName:; Method:Run(); lineNo:0; ilOffset:4.
FileName:; Method:System.Threading.IThreadPoolWorkItem.ExecuteWorkItem(); lineNo:0; ilOffset:0.
FileName:; Method:Dispatch(); lineNo:0; ilOffset:162.
-------- exception.InnerException.ToString() -------
System.Data.SqlClient.SqlException (0x80131904): The INSERT statement conflicted with the FOREIGN KEY constraint "fk__ADHC_HostDisk__ADHC_ClusterDisk". The conflict occurred
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
ClientConnectionId:0fca7b02-93ca-4a31-b609-0b6244178b6a
--------------- exception.StackTrace ---------------
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.Adhc.HostDisk.InsertIntoDB(HostDiskData data, SqlContext ctx)
at Microsoft.VirtualManager.DB.Adhc.HostDisk.CreateInstance(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.DB.Adhc.Host.CreateHostDisk(HostDiskData data, SqlContext ctx, Guid taskID)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.<>c__DisplayClassb.<UpdateDiskAndVolumeInfo>b__6(HostDiskData d, SqlContext ctx)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDbObjects[TObj,TObjData](List`1 existing, List`1 fresh, ObjectDataComparer`2 isEqual, NewObjectCreator`2 createNew, SqlContext ctx, Guid taskID, Boolean deleteNonExisting, Boolean
ignoreDeleteErrors, List`1 skipExistingOnDelete)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDiskAndVolumeInfo(Host host, List`1 existingDisks, List`1 refreshedDisks, List`1 existingVolumes, List`1 refreshedVolumes, Dictionary`2 volumeToDiskMap, CarmineObjectType serverType,
Guid serverId, Nullable`1 hostGroupId, Guid taskID, SqlContext context, Boolean deleteNonExisting, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostDatabaseUpdater.UpdateDatabase()
at Microsoft.VirtualManager.Engine.Adhc.HostRefresher.UpdateAllInformation(Host host, HostUpdateInformation hostUpdateInfo, ITaskContext taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.UpdateDb(HostClusterProperties refresher, HostCluster cluster, List`1 hosts, Dictionary`2 lockedHosts, ClusterUpdateInformation clusterInfo, List`1 hostInfos, Guid taskID, ITaskContext
taskContext)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.HostClusterRefresher.RefreshLockedCluster(HostCluster cluster, List`1 hosts, ITaskContext taskContext, Guid subtaskID, Guid taskId, Int32 recursionNesting)
at Microsoft.VirtualManager.Engine.Adhc.RefreshHostClusterSubtask.RunSubtask()
at Microsoft.VirtualManager.Engine.TaskRepository.SubtaskBase.Run()
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
------------- StackTrace from handler --------------
This is the call stack from where the exception was caught, not where it was thrown.
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.WriteReportTextFile(TextWriter reportFile)
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonExceptionReport.Send()
at Microsoft.VirtualManager.Utils.Diagnostics.WatsonCenter.ReportException(Exception e, WERReportOptions options, String& localReportPath)
at Microsoft.VirtualManager.Engine.TaskRepository.Task`1.SubtaskRun(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
-------------------- Assemblies --------------------
mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Module=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll
Version=4.0.30319.34003
BuildType=retail
Product=Microsoft® .NET Framework
VMMService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\vmmservice.exe
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.ServiceProcess, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceProcess\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System\v4.0_4.0.0.0__b77a5c561934e089\System.dll
Version=4.0.30319.34003
BuildType=retail
Product=Microsoft® .NET Framework
TraceWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\TraceWrapper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Utils, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Utils.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NativeMethods, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NativeMethods.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Common, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Common.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.IndigoAccessLayer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.IndigoAccessLayer.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Core\v4.0_4.0.0.0__b77a5c561934e089\System.Core.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Skuhelper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Skuhelper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Errors, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Errors.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Remoting, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Remoting.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Runtime.Serialization, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Runtime.Serialization\v4.0_4.0.0.0__b77a5c561934e089\System.Runtime.Serialization.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Data\v4.0_4.0.0.0__b77a5c561934e089\System.Data.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.Configuration, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Configuration\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.DirectoryServices.AccountManagement, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices.AccountManagement\v4.0_4.0.0.0__b77a5c561934e089\System.DirectoryServices.AccountManagement.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel\v4.0_4.0.0.0__b77a5c561934e089\System.ServiceModel.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.Adhc.Operations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Adhc.Operations.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.TaskRepository, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.TaskRepository.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ImgLibEngine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ImgLibEngine.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VmmHelperHost, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VmmHelperHost.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VirtualizationInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VirtualizationInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
NetworkServiceInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\NetworkServiceInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
ClusterUtil, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\ClusterUtil.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
VMWareImplementation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\VMWareImplementation.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManager, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManager.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.AuthorizationManagerTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.AuthorizationManagerTasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Backup, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Backup.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.BitBos, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.BitBos.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Version=6.3.9600.16394
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
WsManWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WsManWrappers.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
SqmWrapper, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\SqmWrapper.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Deployment, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Deployment.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement.ResourceModel, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.ResourceModel.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ImgLibOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ImgLibOperation.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Xml\v4.0_4.0.0.0__b77a5c561934e089\System.Xml.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.CustomProperties, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomProperties.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.VmOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.VmOperations.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.MomDal, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.MomDal.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Web.Services, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Web.Services\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.PxeServer, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PxeServer.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Placement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Placement.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.P2VCommon, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.P2VCommon.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
PatchExtractor, Version=0.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\PatchExtractor.dll
Engine.ConfigurationProviders, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ConfigurationProviders.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GatewayInterfaces, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GatewayInterfaces.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.Management.Infrastructure\v4.0_1.0.0.0__31bf3856ad364e35\Microsoft.Management.Infrastructure.dll
Version=6.3.9600.16384
BuildType=retail
Product=Microsoft (R) Windows (R) Operating System
Microsoft.CapacityManager.Modeling.Store.ModelLibrary, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Microsoft.CapacityManager.Modeling.Store.ModelLibrary.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CustomPropertyTasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CustomPropertyTasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.UMOperation, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UMOperation.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Scheduler.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.Tasks, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.Tasks.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.ServiceOperations, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.ServiceOperations.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
GoalState, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\GoalState.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.CloudService, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.CloudService.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
WSManAutomation, Version=3.2.7510.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WSManAutomation.dll
wmiWrappers, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\WMIWrappers.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Transactions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.Transactions\v4.0_4.0.0.0__b77a5c561934e089\System.Transactions.dll
Version=4.0.30319.33440
Product=Microsoft® .NET Framework
System.EnterpriseServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_64\System.EnterpriseServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.Wrapper.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
DB.DelegatedAdmin, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.DelegatedAdmin.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
DB.TieredPerfCounters, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\DB.TieredPerfCounters.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
SMDiagnostics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\SMDiagnostics\v4.0_4.0.0.0__b77a5c561934e089\SMDiagnostics.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.Numerics, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Numerics\v4.0_4.0.0.0__b77a5c561934e089\System.Numerics.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.PhysicalMachine, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.PhysicalMachine.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.DirectoryServices, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.DirectoryServices\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
System.ServiceModel.Internals, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.ServiceModel.Internals\v4.0_4.0.0.0__31bf3856ad364e35\System.ServiceModel.Internals.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.UpdateManagement, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.UpdateManagement.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
Engine.RunAs, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.RunAs.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
System.Management, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Location=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Module=C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Management\v4.0_4.0.0.0__b03f5f7f11d50a3a\System.Management.dll
Version=4.0.30319.33440
BuildType=retail
Product=Microsoft® .NET Framework
Engine.DB.Scheduler, Version=1.0.523.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Location=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
Module=C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\Bin\Engine.DB.Scheduler.dll
Version=3.2.7510.0
BuildType=retail
Product=System Center Virtual Machine Manager 2012 R2
--------- Extra Data for Watson Report -------------
Error Reporting Enabled=True
*** Extra Data ***
Process ID = 1992 (0x07c8)
Managed Thread ID = 10
Native Thread ID = 3880 (0x0f28)
I'd aprreciate your help in resolving this asap
P.S. It's a SCVMM 2012 R2 U1. The SQL script mentioned in the Rollup's page was also run as instructed.
Eran.The key error is here: Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again
Have you verified SQL connectivity, database connectivity, the user account used to connect, the SCVMM computer account used to connect, etc?
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
Disclaimer: Attempting change is of your own free will. -
Write-Behind, Expiration, and SQL Exceptions.
Hi Chaps,
If a cache with write-behind enabled has problems writing to the DB I understand that Coherence will re-queue the objects and write them when the DB is available.
The problem I have is that (after a DB failure) I don't see them being written - I can see these items in the cache but not in the DB, even several hours after the outage. (Items that were added to the cache after the outage are being written).
Is there anything the cachestore methods (specifically store() ) need to do with regards to exceptions to ensure that these items are re-qeueued?
Next question is: I was also wondering how is this managed with regards to expiry?
We have our own expiry routine which removes items from the cache that are older than 24 hours (this was from before we could expire objects by specifying the timeout in the put() method call, which I am intending to switch to).
If an item has not been written to the DB due to an outage and is then expired (by our own routine or by Coherence) is it then lost forever, or will it remain in the queue? (seeing as the queue holds references I am guessing not but though I'd check).
Thanks,
Randal.Jon,
I have a question related to this...If you remember a few weeks back, I stumbled upon the problem of the "version-persistent" map for the versioned-backing-map-scheme does not accept putAll operations. The workaround until you guys implement it, was to override the putAll method of the cacheStore and throw and unsupported operation exception (to force individual puts).
Well, although this workaround works, I am getting tons and tons of:
2006-04-06 17:18:27.347 Tangosol Coherence 3.1/339 <Warning> (thread=WriteBehindThread:MyCacheStore, member=1): The CacheStore "MyCacheStore@46b9979b" does not support storeAll().
2006-04-06 17:18:27.348 Tangosol Coherence 3.1/339 <Error> (thread=WriteBehindThread:MyCacheStore, member=1): Failed to store keys="[16, 18, 21, 26, 5, 13, 14, 25, 17, 15, 23, 19, 2, 6, 9, 7]":
java.lang.UnsupportedOperationException
at ...MyCacheStore.storeAll(MyCacheStore.java:126)
at com.tangosol.net.cache.ReadWriteBackingMap$CacheStoreWrapper.storeAll(ReadWriteBackingMap.java:3820)
at com.tangosol.net.cache.ReadWriteBackingMap$WriteThread.run(ReadWriteBackingMap.java:3538)
at com.tangosol.util.Daemon$1.run(Daemon.java:63)
2006-04-06 17:18:27.349 Tangosol Coherence 3.1/339 <Warning> (thread=WriteBehindThread:MyCacheStore, member=1): Requeued store for key="16"
2006-04-06 17:18:27.349 Tangosol Coherence 3.1/339 <Warning> (thread=WriteBehindThread:MyCacheStore, member=1): Requeued store for key="18"
2006-04-06 17:18:27.350 Tangosol Coherence 3.1/339 <Warning> (thread=WriteBehindThread:MyCacheStore, member=1): Requeued store for key="21"
2006-04-06 17:18:27.351 Tangosol Coherence 3.1/339 <Warning> (thread=WriteBehindThread:MyCacheStore, member=1): Requeued store for key="26"
the first OperationNotSupported is expected, but I'm not sure what the requeued warnings are all about. These are not failures to the DB...it is something else. (mind you that this happens when trying to load a lot of data into the map.)
1- Is this requeuing related or the same as in failed DB stores?
2- Is it possible to "lose" stores if I don't configure the write-requeue-threshold with very, very high values? I must ensure I don't lose anything.
In a related note, in some circumstances, I need to ensure that the "write queue" is flushed or cleared. For example, I may want to force a flush of all pending stores (and wait/block until that's done).
I have looked into it and I don't seem to know how to do it. I can read the write-queue length, but I believe that this is not very accurate...since my tests seem to indicate that the write-behind thread may take the entries to store off the write-queue and then deal with them in parallel (which means that there are still entries althought the write-queue size is 0). Also, there are some calls from the cache store that, at first, seem to give some access to the write thread (potentially allowing me to contact the thread to tell him to flush or discard any pending stores)...but I believe that all of the functions are protected...but there may be other ways..
I guess my second batch of questions are:
1- How can I effectively force a flush (or clear) of the pending stores. Such that there is no single store pending in any queue (visible or invisible to the programmer).
2- What is the role of re-queuing in these situations? where is the queue sitting, the thread? the cache store? who's responsible of retrying that, and when?...I would like to flush those entries too.
A quick explanation of the operation of the write thread would also be very appreciated.
Thanks!
Josep M. -
Cache write-behind complete check
Is there a surefire way to check a cache that has a store persisting objects to the database and write-behind set to 2 seconds, has persisted all objects put into the cache?
We have tried using JMX, querying the Cache's QueueSize and waiting until it reaches 0. It turns out that when putting objects into the write-behind cache, the write-behind queue is not necessarily non-zero immediately after the put(s). e.g. QueueSize may be 0, even if objects still need to be persisted.
For our nightly integration tests we need to clear out the cache, but want to make sure we do not call NamedCache.clear() on a cache that still has objects that need to be persisted.
Any ideas?Hi Rob,
The problem may actually be the timeliness of updates to the QueueSize JMX attribute as we're using the MBeanConnector to obtain information on our cache members (and providers). Assuming that objects actually make it to the write-behind queue during the cache put call and certain tests need to be sure these objects are persisted, instead of doing the accounting approach discussed previously, I found a forum thread on ReadWriteBackingMap flush calls.
To get access to the ReadWriteBackingMap.flush() I created a small test today using a subclass of ReadWriteBackingMap that registers the backingmap with our CashStore implementation:
protected void configureCacheStore(CacheStore store, boolean readOnly) {
super.configureCacheStore(store, readOnly);
if (store instanceof CacheLoaderWriterProvider) {
((CacheLoaderWriterProvider)store).registerBackingMap(this);
}Our cachstore (CacheLoaderWriterProvider) in turn exposes a call to the registered map's flush method as a JMX operation.
Whenever we need to be sure the write-behind queue is empty during our tests, we'll call this JMX operation.
Best Regards,
Marcel. -
Can a db slowdown with write-behind cause a slowdown in cache operations?
If we have a coherence cluster, and one cache configured with write-behind is having trouble writing to the db (ie, it's slow), and we keep adding objects to the cache that exceed the ability of the db to consume them; will flow-control kick in and cause the writes to the cache to block/slow-down? Ie, the classic producer-consumer problem, where we are adding objects to the cache, faster than the cachestore can consume them.
What happens in this case? Will flow-control kick in and block writes to the cache? Will an internal buffer just keep growing? Are there any knobs to tweak this behavior (eg, in the case of spikes, where temporarily the producer is producing faster than the consumer can consume for a brief period of time, but then things go back to normal)?user9222505 wrote:
I believe we discovered that the same thread pool is used for all requests to the cache, including gets, puts and calls into the cachestore. So if the writes are slow within the cachestore, then it uses up all of the threads and slows everything down.Hi,
This is not really correct.
If a cache in a service is configured to use write-behind then a separate thread for that service is started, which deals with write-behind store and storeAll operations.
The remove operations need to be handled synchronously to avoid corruption of the data-set in the scenario of reading a entry from the cache immediately after removing it (if it were not synchronously deleted from the backing storage, then reading it back could give an incorrect non-null value). Therefore remove operations are handled synchronously on the service / worker thread, and not delayed on the write-behind thread.
Gets are also synchronously handled, so they again are served on the service / worker thread.
So if the puts are slow and wait too much, that may delay other puts but should not contend with other threads. If the puts are computation intensive, then obviously they hinder other threads because of consumption of the same CPU resource, and not simply because they execute.
Best regards,
Robert
Maybe you are looking for
-
SQL Expressions, commands and more
Hello: I have several reports I need to create in Crystal Reports XI, and I'm not sure of the best methodology. I have an ASA (Adaptive Server Anywhere) 9.02 database that I am connecting to through ODBC. The main part of the query is fairly straig
-
Difficulty Printing PNG to HP Printer
I am trying to print a CS4 Photoshop PNG file from a Mac to an HP Color Laserjet 3700. The file's background is transparent and prints white from InDesign CS4 and also Word applications (which is what I want). However, when printed from Photoshop CS4
-
Hi , I have enabled the check box for display description in NC Client maintenance. There by I can see the Descriptions along with NC codes in NC Code lists.But when I assign NC code (after I click ADD button) I can see only NC code not the descript
-
Captivate 3 Trial Safe to Install Alongside Captivate 2?
I have XP SP2 and am having a heck of a bad time with Captivate 2 being very unstable. Is it safe to download and use the Captivate 3 trial version without removing Captivate 2?
-
Help needed for missing VC# Templates
Hello, i recently installed Visual Studio 2013 pro u4 and everything went fine during the install. But now when i create a new project for visual C#(every template) it tells me my Visual C# Project System Package did not load properly. I hve tried to