When migrating a Non English Vault Database to Vault 2011, an error is encountered and the migration stops. The entry in the German vlog is as follows:-
Event Processing: Error raised while executing scheduled event: Autodesk.Lock.Vacuum
Exception: DatabaseError [109]
Stacktrace:
Server stack trace:
Exception rethrown at [0]:
bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
bei Connectivity.Product.Services.ItemService.c()
bei Connectivity.Product.EventMonitor.LockVacuum.Execute(ScheduledEvent scheduledevent)
bei Connectivity.Core.EventMonitor.Scheduler.b(ScheduledEvent A_0)
bei Connectivity.Core.EventMonitor.Scheduler.a(Object A_0)Exception(Inner): Bei der Konvertierung eines char-Datentyps in einen datetime-Datentyp liegt der datetime-Wert außerhalb des gültigen Bereichs.
Die Anweisung wurde beendet.
Stacktrace(Inner): bei Connectivity.Core.Database.TransactionContext.OnSqlException(SqlException e)
bei Connectivity.Core.Database.SqlAccess.e(SqlCommand A_0)
bei Connectivity.Core.Database.SqlAccess.ExecuteNonQuery(CommandType commandType, String commandText, Int32 commandTimeout, SqlParameter[] commandParameters)
bei Connectivity.Core.DataAccess.Director.a()
bei Connectivity.Core.DataAccess.Director.Execute(Options options)
bei Connectivity.Product.DataAccess.Items.RemoveExpiredLocks()
bei Connectivity.Product.Services.ItemService.c()
bei System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)
bei System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
The solution is to install and start SQL Management Studion and change the "Default Language" for the ADMS-<COMPUTERNAME> and VaultSys user accounts to English.
Subscribe
GREAT! I spent several days to figure out what this error message is all about. Now our migration worked like a charme! AWESOME!
Posted by: Mario | August 27, 2010 at 04:53 PM
Hi, we encounter this error too, with a French version. Your post is dated from May 2011, was an hotfix actually released for this?
Posted by: Marina | October 25, 2010 at 09:15 AM
I cannot find that we did release a Hotfix for this Marina. So this is the solution and I have updated the wording above to reflect this.
Posted by: Richard | October 25, 2010 at 10:00 AM