Slicing does not work because of a Linq exception
Reference Number: AA-00426 Created: 07-03-2013 14:18 Last Updated: 07-03-2013 14:18 0 Rating/ Voters

Title: Slicing does not run because of a Linq exception.

Description: On a memoQ server you are trying to slice a document, but you are getting the error message below.

TYPE:
System.InvalidCastException

MESSAGE:
Specified cast is not valid.

SOURCE:
System.Data.Linq

CALL STACK:

Server stack trace: 
   at System.Data.Linq.IdentityManager.StandardIdentityManager.SingleKeyManager`2.TryCreateKeyFromValues(Object[] values, V& v)
   at System.Data.Linq.IdentityManager.StandardIdentityManager.IdentityCache`2.Find(Object[] keyValues)
   at System.Data.Linq.ChangeProcessor.GetOtherItem(MetaAssociation assoc, Object instance)
   at System.Data.Linq.ChangeProcessor.BuildEdgeMaps()
   at System.Data.Linq.ChangeProcessor.SubmitChanges(ConflictMode failureMode)
   at System.Data.Linq.DataContext.SubmitChanges(ConflictMode failureMode)
   at MemoQ.Networking.BLL.ServerProject.ServerProjectManager.DivideDocument(Guid serverProjectGuid, Guid documentGuid, DocumentRangeInfo[]
documentRanges)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean
fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at MemoQ.Networking.Common.ServerProject.IServerProjectManager.DivideDocument(Guid serverProjectGuid, Guid documentGuid, DocumentRangeInfo[]
documentRanges)
   at MemoQ.Project.ProjectSourceFilesControl.divideToolStripMenuItem_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Fix: This is a Windows-related exception that you can fix by applying the following Microsoft hotfix:

http://hotfixv4.microsoft.com/.NET%20Framework%203.5%20-%20Windows%20Server%202003,%20WindowsXP,%20Windows%20Vista,%20Windows%20Server%202008%20(MSI)/sp1/DevDiv975687/30729.5821/free/448814_intl_i386_zip.exe

is for 32 bit systems, 

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=963657&kbln=en-us is for 64 bits.

The patch has to be applied to the server.

Rss Comments (Please do not post support requests here.)
  • There are no comments for this article.
Info Add Comment
Nickname: Your Email: Subject: Comment:
Enter the code below:
Quick Jump Menu
Info Missing an article? Let us know!