From: Edward Mitchell on 9 Jul 2007 21:17 A message is popping up "An invalid argument was encountered." when the user clicks on the File menu item. I have an MDI app and it appears that the message occurs before any document is selected. When a document file has been opened, the message also pops up, again when the File menu is clicked. The file menu itself never opens. I found the place in VS .NET 2005 that is producing the message: - afxres.rc with the line: AFX_IDS_INVALID_ARG_EXCEPTION "An invalid argument was encountered." The code that uses this seems to be in except.cpp as: IMPLEMENT_DYNAMIC(CInvalidArgException, CException) CInvalidArgException _simpleInvalidArgException(FALSE, AFX_IDS_INVALID_ARG_EXCEPTION); How we get here is not obvious! This occurs in a release build, noticed by two users. The problem doesn't occur on any machine that I have available. I presume the problem is occurring with the OnUpdate... message handlers are running through all the submenu items under File. However, most users have no problem. The failure itself is also not consistent in that the user can actually open a document so not all File selections result in the message box. Is there somewhere in the message loop that I can put in trace messages to try and pin down what is happening? Ed -- Edward E.L. Mitchell Phone: (508)771-0806 500 Ocean St., Unit 134, Hyannis, MA 02601
From: Charles Wang[MSFT] on 10 Jul 2007 02:39 Hi Edward, I understand that two users encountered the error message "An invalid argument was encountered." when they used your released application. However this issue could not be reproduced under any of your machines. If I have misunderstood, please let me know. From the issue appearance, it is most likely related to missing correct version libraries. I would like to know how you deployed your application. What is the result if you make a setup program to deploy your application? Also, you may recommend your users to use Process Explorer to monitor the process to see if there are some helpful clues in the trace log. You may compare their trace logs to yours. The tool can be downloaded via: Process Explorer for Windows v10.21 http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx Please feel free to let me know if you have any other questions or concerns. Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
From: Edward Mitchell on 10 Jul 2007 10:47 Charles. You are correct about the message originating conditions. The app was deployed by creating a Setup project in VS.NET 2005 so that there is a Setup.exe and a .msi file. The .zip file is at www.racesail.org/rs40.zip. I downloaded the Process Explorer but I don't see a mechanism to see a trace of the windows messages. I can see a list of .dlls (that are more than the dlls that were included in the .msi setup file) but no knowledge of what is happening when I select the File menu. I can use Spy++ to get a long list of messages. This is a list of some of the messages for the select of the File menu but the messages are filtered to just show the Non-client message group: .... <00050> 00120218 P WM_NCMOUSEMOVE nHittest:HTMENU xPos:601 yPos:697 <00051> 00120218 S WM_NCHITTEST xPos:601 yPos:697 <00052> 00120218 R WM_NCHITTEST nHittest:HTMENU <00053> 00120218 S WM_NCACTIVATE fActive:True <00054> 00120218 R WM_NCACTIVATE <00055> 00120218 S WM_NCACTIVATE fActive:False <00056> 00120218 R WM_NCACTIVATE fDeactivateOK:True <00057> 00120218 P WM_NCLBUTTONDOWN nHittest:HTMENU xPos:601 yPos:697 <00058> 00120218 P WM_NCMOUSELEAVE <00059> 00120218 S WM_NCPAINT hrgn:79041A67 <00060> 00120218 R WM_NCPAINT <00061> 00120218 S WM_NCACTIVATE fActive:False <00062> 00120218 R WM_NCACTIVATE fDeactivateOK:True .... This shows the LBUTTONDOWN message. There are a lot more messages actually being generated that are filtered away. But all these messages are going through the MFC message map process and one must be causing the problem - but not on my machine :( Ed "Charles Wang[MSFT]" <changliw(a)online.microsoft.com> wrote in message news:MjHMZ0rwHHA.4308(a)TK2MSFTNGHUB02.phx.gbl... > Hi Edward, > I understand that two users encountered the error message "An invalid > argument was encountered." when they used your released application. > However this issue could not be reproduced under any of your machines. > If I have misunderstood, please let me know. > > From the issue appearance, it is most likely related to missing correct > version libraries. I would like to know how you deployed your application. > What is the result if you make a setup program to deploy your application? > > Also, you may recommend your users to use Process Explorer to monitor the > process to see if there are some helpful clues in the trace log. You may > compare their trace logs to yours. > The tool can be downloaded via: > Process Explorer for Windows v10.21 > http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx >
From: Charles Wang[MSFT] on 11 Jul 2007 04:30 Hi Ed, I installed your application on my two machines, one is Windows XP SP2, the other is Windows Server 2003 x64 SP1; however the issue could not be reproduced on either of the machine. Your application worked fine. You may confirm with your customer to see if there were some special softwares such as anti-virus software installed on their computer. What is the result if the disable them? Appreciate your understanding that since this issue ocurred only on two of your customers' machines and it is hard for us to reproduce the issue, dump analysis may be required to track the root cause. However this work can only be done by CSS. If this issue is urgent to your business, effectively and immediately I recommended that you contact Microsoft Customer Support Services (CSS) to perform dump analysis. Please be advised that contacting phone support will be a charged call. To obtain the phone numbers for specific technology request please take a look at the web site listed below. http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS If you are outside the US please see http://support.microsoft.com for regional support phone numbers. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
|
Pages: 1 Prev: Memory leak with CAsyncSocket::Create Next: CFileDialog and "My Computer" |