Hey,
I tried to update VAMT for Windows 8.1 to Windows 10 (Version 10.1.10.586.0).
When I'm starting VAMT, I'm getting the following error message:
"String or binary data would be truncated. The statement has been terminated".
In the event viewer, I also have this error:
Error while performing calling asynchronous routine Void ServiceVamtDatabaseThreadProc(System.Object) operation: System.Data.SqlClient.SqlException (0x80131904): String or binary data would be truncated.
The statement has been terminated.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.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 System.Data.Linq.SqlClient.SqlProvider.Execute(Expression query, QueryInfo queryInfo, IObjectReaderFactory factory, Object[] parentArgs, Object[] userArgs, ICompiledSubQuery[] subQueries, Object lastResult)
at System.Data.Linq.SqlClient.SqlProvider.ExecuteAll(Expression query, QueryInfo[] queryInfos, IObjectReaderFactory factory, Object[] userArguments, ICompiledSubQuery[] subQueries)
at System.Data.Linq.SqlClient.SqlProvider.System.Data.Linq.Provider.IProvider.Execute(Expression query)
at System.Data.Linq.ChangeDirector.StandardChangeDirector.DynamicInsert(TrackedObject item)
at System.Data.Linq.ChangeDirector.StandardChangeDirector.Insert(TrackedObject item)
at System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode failureMode)
at System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode
at Microsoft.Licensing.VolumeActivation.CilXImporter.ImportVamtSystemData(VamtDataContext vamtData, VamtSystemData incomingSystemData, IWaitProgressHelper progressHelper, Boolean servicing)
at Microsoft.Licensing.VolumeActivation.CilXImporter.ImportVolumeActivationManagementToolData(VamtDataStore dataStore, VolumeActivationManagementToolData data, IWaitProgressHelper progressHelper, Boolean servicing)
at Microsoft.Licensing.VolumeActivation.CilXImporter.TryImportCilX(VamtDataStore dataStore, String fileName, IWaitProgressHelper progressHelper, Boolean servicing)
at Microsoft.Licensing.VolumeActivation.Presentation.VamtSnapIn.ServiceVamtDatabaseThreadProc(Object job)
ClientConnectionId:a4f45101-705a-41ba-bda6-879aef72bca0
Despite those errors, VAMT is running as it should so far...
Do you have any recommendation to get ride of those problems?
Thanks