![]() ![]() When they came in the next day then this exception had happened. Regarding (2): one person said all they did was leave our software running overnight (a very common scenario) showing a very common section of our software. If it were something like Window.Title being too long then the exception would very likely happen again. Regarding (1): since I don't yet have a known reproduction, that means that when people go back to the same place and do the same things as they were doing when the exception happened then it doesn't happen again. I think it's very unlikely for two reasons: ![]() Thank you, it be possible that your window has an extraordinary long title? I do not believe SQL Server is/was present on this machine. Internet search results currently point to some issue with an out-of-date installation of SQL Server. Message: The data area passed to a system call is too small.Īt MS.(HandleRef hWnd, StringBuilder lpString, Int32 nMaxCount)Īt .WindowAutomationPeer.GetNameCore()Īt .AutomationPeer.UpdateSubtree()Īt ()Īt ()Īt (Object arg)Īt .FireInvokeOnRenderCallbacks()Īt .RenderMessageHandlerCore(Object resizedCompositionTarget)Īt .RenderMessageHandler(Object resizedCompositionTarget)Īt .InternalRealCall(Delegate callback, Object args, Int32 numArgs)Īt .Tr圜atchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |