reporting services configuration manager unhandled exception has occurred your application

How to Fix the "Unhandled Exception Has Occurred in Your Application" Error on Windows

If your apps have issues running, here's how to fix unhandled exceptions on Windows.

Windows has a lot of error messages, but some of them are less descriptive than others. For example, you may come across the "unhandled exception has occurred in your application" error.

However, it's not too tough to resolve this unhandled exception error. As such, if you encounter it, try the following tricks to fix the issue.

What Does the "Unhandled Exception Has Occurred in Your Application" Error Mean?

An exception is an unexpected event or situation when a computer program runs. Think of it as an unscheduled happening or error that interrupts whatever you're doing.

Windows has inbuilt exception handling features whenever an error like this occurs. However, sometimes an unhandled exception occurs when a computer program or application does not properly handle exceptions.

You can face the "unhandled exception has occurred in your application" error while working on applications or playing games. You can also experience it while opening a file or when you've just started up your PC.

This error can occur if the .NET Framework is damaged or if there are some corrupt files or malware on your system.

When this happens, you'll see a Microsoft .NET Framework window pop up on your PC screen, alerting you that an "Unhandled error has occurred in your application" . Annoyingly, this window will keep appearing even after you close it and until you've fixed the error.

So let's explore the fixes you can try to quickly resolve this error and get back to working smoothly again.

1. Install the Latest Windows Updates

You would be aware that Microsoft regularly releases updates for the Windows OS. It's important to keep your Windows PC updated and running the latest version to continue enjoying a hassle-free computing experience.

These updates not only enable you to experience new features but are also essential as they fix bugs and vulnerabilities to keep your Windows experience safe and secure.

To ensure that, check out the ways how you can install Windows updates on your Windows 11 PC .

2. Scan for Malware Using Microsoft Defender or Your Antivirus

There is a possibility that the "Unhandled exception has occurred in your application" error could be caused by malware. To rule that out, you should scan your computer with the inbuilt Microsoft Defender antivirus.

Check out our guide to learn how to scan your PC for malware with the Microsoft Defender . Or if you've installed a third-party antivirus on your PC, use that to scan for malware.

3. Run the .NET Framework Repair Tool

One of the most probable causes of the "Unhandled exception has occurred in your application" error is problems in the .NET Framework.

To set them right, download and run the .NET Framework Repair tool from the official Microsoft website .

Once the tool has been downloaded on your PC, take the following steps:

• Double-click on the downloaded file and click Yes on the UAC prompt
• Now, restart your computer.

4. Enable the .NET Framework

If running the .NET Framework Repair Tool didn't fix the error, try enabling the .NET Framework.

5. Use System File Checker on Windows

Since corrupted files can also cause the "unhandled exception has occurred in your application" error, you can try running the System File Checker or SFC scan. You can easily learn how to do that in our guide on how to run the SFC tool on Windows .

Be patient as the SFC scan will take a few minutes. If the unhandled exception error was caused by corrupt files, you will see that the SFC would have scanned and fixed it.

Clear Your Windows System of the "Unhandled Exception Has Occurred in Your Application" Error

The "Unhandled exception error has occurred in your application" can interrupt the smooth flow of your work on Windows. Using the above methods, you'll be able to fix this error and its annoying pop-ups.

• Power BI forums
• News & Announcements
• Get Help with Power BI
• Report Server
• Power Query
• Mobile Apps
• DAX Commands and Tips
• Custom Visuals Development Discussion
• Health and Life Sciences
• Power BI Spanish forums
• Translated Spanish Desktop
• Power Platform Integration - Better Together!
• Power Platform Integrations (Read-only)
• Power Platform and Dynamics 365 Integrations (Read-only)
• Training and Consulting
• Instructor Led Training
• Dashboard in a Day for Women, by Women
• Community Connections & How-To Videos
• COVID-19 Data Stories Gallery
• Themes Gallery
• Data Stories Gallery
• R Script Showcase
• Webinars and Video Gallery
• Quick Measures Gallery
• 2021 MSBizAppsSummit Gallery
• 2020 MSBizAppsSummit Gallery
• 2019 MSBizAppsSummit Gallery
• Custom Visuals Ideas
• Upcoming Events
• Community Blog
• Power BI Community Blog
• Custom Visuals Community Blog
• Community Support
• Community Accounts & Registration
• Using the Community
• Community Feedback

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge .

• Re: Report Server Configuration Manager fails to s...
• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Printer Friendly Page
• All forum topics
• Previous Topic

• Mark as New
• Report Inappropriate Content

Report Server Configuration Manager fails to start with .NET Framework error

Solved! Go to Solution.

• Configuration Manager

View solution in original post

Helpful resources

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members. Please post your questions in the correct category.

• Endpoint Manager
• Configuration Manager

SOLVED   Microsoft.ConfigurationManagement has stopped working

• Thread starter ShaneW07
• Start date Oct 20, 2021
• Oct 20, 2021

Hi all, this is my first time posting here, so hopefully this is the right place... I'm running System Center Configuration Manager Version 2107 (5.00.9058.1000) and currently when I open the management console on the server itself or a remote machine it opens with the following error "Microsoft.ConfigurationManagement has stopped working" and then gives me the following options "Debug" or "Close Program". Clicking Debug gives the following dialog box "Visual Studio Just-In-Time Debugger", which states 'An unhandled Microsoft .NET Framework exception occurred in Microsoft.ConfigurationManagement.exe [6352]. Just-In-Time debugging this exception failed with the following error: No installed debugger has Just-in-Time debugging enabled. In Visual Studio, Just-In-Time debugging can be enabled from Tools/Options/Debugging/Just-In-Time." The console does briefly load and the only thing that shows in the console is Administration. I did the below and after the below the error above started to occur, as it was only a Site Role being added I did not take a VM Snapshot, very silly of me, I regret this now! I was installing the Site Role "Reporting services point" according to the following logs installing the role was successful on the server, "srsrpsetup.log" and "srsrpMSI.log", after adding the Site Role I tried to head to Reports and it was still blank and when creating a report it would say the role needed to be installed, so I assumed the console needed to be closed and reopened to take effect, however, upon doing this I then received the error above. When opening the console the following three logs are created in Event Viewer: Application Error " Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.2107.1063.1000, time stamp: 0x904f05b2 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1202, time stamp: 0x448a4f5d Exception code: 0xe0434352 More of this log can be provided if required. " .NET Framwork " Application: Microsoft.ConfigurationManagement.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentException More of this log can be provided if required. " Critical " System.ArgumentException: Version string portion was too short or too long. at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument) at System.Version.TryParseVersion(String version, VersionResult& result) at System.Version.Parse(String input) at System.Version..ctor(String version) More of this log can be provided if required. " I have already tried reinstalling the console on both the server and the remote machine, I have also tried installing the latest version of .NET Framework and I have tried running the .NET repair tool. Sadly none of these were successful. I will try my best to provide any logs requested and would be extremely grateful for any help or advice. Thanks  

Prajwal Desai said: You should have used online guides or hired a consultant for this. From what I see, you are more concerned about the reports than ConfigMgr. First fix the console crash issue, and you can then reinstall the reporting services. Click to expand...

Prajwal Desai

Forum owner.

When you upgraded to ConfigMgr 2107, did you not get Dot NET 4.8 Framework warning - https://www.prajwaldesai.com/fix-sccm-dot-net-4-8-prerequisite-warning/ Configuration Manager requires at least .NET version 4.6.2, but recommends the latest version 4.8. A later version of Configuration Manager will require .NET version 4.8. To minimize disruption, before you run Configuration Manager setup, update .NET and restart the system.  

• Thread Starter

Prajwal Desai said: When you upgraded to ConfigMgr 2107, did you not get Dot NET 4.8 Framework warning - https://www.prajwaldesai.com/fix-sccm-dot-net-4-8-prerequisite-warning/ Configuration Manager requires at least .NET version 4.6.2, but recommends the latest version 4.8. A later version of Configuration Manager will require .NET version 4.8. To minimize disruption, before you run Configuration Manager setup, update .NET and restart the system. Click to expand...

If the console is reporting this error both on server and remote machine (with console installed), then I don't think the upgrade is completed. Can you confirm if the upgrade from 2103 -> 2107 was successful ?. I also want you to go to monitoring and verify if all the components are online and healthy. Such issues require access to the ConfigMgr setup because we cannot exactly determine what's causing this. We will try to resolve it here otherwise you can always log a case with MS support.  

Prajwal Desai said: If the console is reporting this error both on server and remote machine (with console installed), then I don't think the upgrade is completed. Can you confirm if the upgrade from 2103 -> 2107 was successful ?. I also want you to go to monitoring and verify if all the components are online and healthy. Such issues require access to the ConfigMgr setup because we cannot exactly determine what's causing this. We will try to resolve it here otherwise you can always log a case with MS support. Click to expand...

If all the components are healthy and online, I don't see a reason why the console shows no reports. Try finding what changes were done recently that triggered this issue. For example, did someone restore the VM, uninstall or repaired a ConfigMgr role etc. I know how it feels when you launch the console, and it crashes with some stupid kernel error. I recommend logging a case with Microsoft support, and the support shall access your setup remotely to get more details about this issue.  

Prajwal Desai said: If all the components are healthy and online, I don't see a reason why the console shows no reports. Try finding what changes were done recently that triggered this issue. For example, did someone restore the VM, uninstall or repaired a ConfigMgr role etc. I know how it feels when you launch the console, and it crashes with some stupid kernel error. I recommend logging a case with Microsoft support, and the support shall access your setup remotely to get more details about this issue. Click to expand...

ShaneW07 said: I sadly didn't know that the SQL Server Reporting Services needed to be installed until after I'd added the Reporting Services Point Site Role, would this causes any issues? Click to expand...

Glad to hear that. Finally, the issue is resolved. Once you determine the ConfigMgr is working fine, take a snapshot. Marking this thread as Solved.  

Well-Known Member

ShaneW07 said: I from now certainly won't be changing any roles without taking a snapshot and looking up some guides. Click to expand...

Garth said: Just to be clear, Snapshots are NOT supported by CM and should NOT be "used" per se. Click to expand...

ShaneW07 said: Thank you for letting me know, hopefully they are only ever their as a last resort. Click to expand...

• Dec 1, 2021

Hi all, and thanks for your sharings. I have exactly the same problem and I am stuck now for three days searching a solution.... with the Console is not working. Please provide any advise that I can move forward.  

saleharaki said: Hi all, and thanks for your sharings. I have exactly the same problem and I am stuck now for three days searching a solution.... with the Console is not working. Please provide any advise that I can move forward. Click to expand...

Latest posts

• Latest: mels_101
• Yesterday at 11:33 PM

• Latest: Prajwal Desai
• Yesterday at 9:11 PM
• Yesterday at 9:10 PM

• Latest: Vavamoose
• Yesterday at 3:31 PM
• Latest: Eliran Aharoni
• Yesterday at 1:03 PM

Forum statistics

Follow along with the video below to see how to install our site as a web app on your home screen.

Note: This feature may not be available in some browsers.

• This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register. By continuing to use this site, you are consenting to our use of cookies. Accept Learn more…

Sign up for our daily newsletter

• Privacy Policy
• Advertise with Us

How to Fix the “Unhandled Exception Has Occurred in Your Application” Error on Windows

Among the many errors you may encounter while working on a Windows 10 or 11 PC is the “Unhandled exception has occurred in your application.” This problem can appear while you’re using an application, playing a game or starting your PC. It usually signals an issue with the .NET Framework or the presence of corrupt files or malware on your system. This tutorial shows you how to clear that error.

Good to know : tired of always depending on Google for your searches? Try these deep web search engines that will unearth more results.

Things to Do First

1. scan for malware, 2. run the .net framework repair tool, 3. enable the .net framework, frequently asked questions.

The first thing you should try, before doing anything else, is to restart your PC. Rebooting your computer can sometimes be the easiest solution to stop seeing this error. If a restart proves ineffective, try running an SFC scan next. System File Checker (SFC) is built in to Windows and can be used to locate and repair lost or corrupt files.

It’s also a good idea to check whether you have any pending updates. Installing the latest version of Windows may be all that’s needed to remove this error from your system.

There is a possibility that the Unhandled Exception error is caused by malware. To rule that out, scan your computer using Windows’s native antivirus solution. The built-in Microsoft Defender is enabled automatically and will keep your PC safe. Follow these steps to check whether Defender is actively protecting your device from attacks:

• Open “Windows Security” from the Start menu to access Microsoft Defender.

• Check under “Virus & Threat Protection” in the Home tab. If it says “No action needed,” your device is already protected by Microsoft Defender.

• If you still want to perform a scan just to ensure your PC isn’t infected, click “Virus & Threat Protection -> Quick scan.”

Tip : still worried about your PC’s safety? Downloading a reputable antivirus program is a good idea.

The error we’re discussing in this tutorial can also be caused by .NET Framework issues. As a result, you may want to repair it by following the steps below.

• Go to the official Microsoft website and download the .NET Framework Repair tool .
• Once the application has finished downloading, double-click the EXE file to launch it.

• Click “Yes” in the User Account Control prompt.
• Check the box that says “I have read and accept the license terms” and click “Next.”

• The application will start a scan to detect any issues.

• In the next window, view the recommended changes. Click “Next” to apply them.

• Restart your computer and check to see whether the error still manifests.

Tip : does your Ethernet speed seem to be capped at 100 Mbps on Windows ? Learn how to remove this limitation.

If the .NET Framework Repair Tool did not resolve the issue, you may want to try restarting it.

• Click on the Start menu and type “Windows Features” into the search bar. Select the “Turn Windows features on or off” result.

• Check the box next to “.NET Framework 3.5” and “.NET Framework 4.8 Advanced Services” in the Windows Features window. Click “OK.”

• In the following window, you may notice a message stating that “Windows requires some files from Windows Update to complete the installation of some features.” Select the “Let Windows Update download the files for you” option.
• Once the process is complete, you’ll see the “Windows completed the requested changes” message. Close the window and restart your PC.

Good to know : sometimes you need to know your router’s IP address . We show you where to find it.

How can I prevent the error from happening again?

Even though it may not be possible to completely avoid the problem, you can try and prevent it by making sure your software and system are always up to date.

Can the "Unhandled Error Has Occurred in Your Application" error cause data loss?

Even though the error itself may not cause data loss, it can be a sign of a bigger problem that could lead to data loss if not fixed. So that the error doesn’t cause greater damage, it should be addressed immediately.

Image credit: Unsplash . All screenshots by Oluwatokiloba Folami

Our latest tutorials delivered straight to your inbox

Oluwatokiloba is a skilled writer and editor who is goal-oriented and innovative. Seeing how far he can go to find new, creative ways to address problems motivates and fascinates him. He likes to workout and listen to music when he is not tinkering.

• Disk & Data Manager
• Partition Wizard
• Power Data Recovery
• ShadowMaker
• Media Toolkit
• uTube Downloader
• Video Converter
• Download Partition Wizard Free Edition: Download Pro Edition: Try Demo Server Edition: Try Demo
• Partition Magic

Resolved: Unhandled Exception has Occurred in Your Application

Have you received the “ unhandled exception has occurred in your application ” error on your computer? Don’t worry. MiniTool software provides you with 5 simple methods to solve this Microsoft .NET Framework unhandled exception.

About Microsoft .NET Framework Unhandled Exception Error

According to the reports on the forum, the “ unhandled exception has occurred in your application ” error often occurs as soon as the computer starts up. If you receive this error, your computer might get frozen or display other symptoms.

This error is usually displayed in a window of Microsoft .NET Framework and is accompanied with an error message, just as the following picture shows.

Focusing on this problem, I will show you 5 solutions with the detailed steps. You should be able to fix the Microsoft .NET Framework unhandled exception error quickly.

Method 1: Scan for Virus

At first, you can make a full scan for your computer to get rid of the possibility of virus attacks. You can use your trusted third-party antivirus program, or Windows Defender .

To scan for virus with Windows Defender, just go to Update & Security > Windows Security > Virus & threat protection , and choose to perform a Full scan .

Method 2: Temporarily Disable Your Antivirus

Besides, your antivirus programs or Windows Defender might also be responsible for this “unhandled exception has occurred in your application” error. For example, some antivirus tools such as Panda Antivirus are known to be a reason for this error.

Thus, it is not a bad idea to temporarily disable all your installed security software.

If the error disappears after disabling your antivirus, it’s time to uninstall your original antivirus and replace it with a reliable and safe one. If the error still exists, you can enable your antivirus again and try the following methods.

Method 3: Clean Boot Your Computer

Apart from your antivirus, other programs or services might also affect the proper functionality of Microsoft .NET Framework suite. To find out the problematic program or service quickly, you can clean boot your computer.

Step 1 : Press Windows + R to invoke Run dialog. Input msconfig and click OK to access System Configuration .

Step 2 : In General tab, choose Selective startup . The three options of it are enabled by default, and you need to uncheck Load startup items .

Step 3 : Switch to Services tab, check Hide all Microsoft services and click Disable all.

Step 4 : Go to Startup tab and click Open Task Manager . When you get the following window, highlight each listed startup item which is enabled and click Disable .

After that, restart your computer to check if the problem disappears.

If the error has been removed, you need to enable these items which are disabled above one by one to find the problematic one. Then, you can disable or uninstall it.

If the error message come forth again, this error should not be caused by your programs or services, but your corrupted Microsoft .NET Framework installation . In this case, you can try following methods.

Method 4: Perform SFC Scan

It has been proven that the corruption of certain important system files can result in that Microsoft .NET Framework gets corrupted. As for the system files issue, you can use System File Check (SFC) to scan and repair your system files.

Step 1 : After invoking Run window, input cmd and press Ctrl + Shift + Enter to open Command Prompt as administrator.

Step 2 : Type the command sfc /scannow and press Enter .

Step 3 : After the operation is completed successfully, restart your computer and check if the error has been fixed successfully.

Method 5: Install the Latest Version of NET Framework

If you cannot fix the “unhandled exception has occurred in your application” error with SFC scan, you might need to install the latest version of NET Framework and then repair it.

Just go to Microsoft official website to download the latest version and run it on your computer. Then, follow the steps below to check its integrity.

Step 1 : Type control.exe in Run window and click OK to open Control Panel .

Step 2 : Go to Uninstall a program and click Turn Windows features on or off .

Step 3 : In the pop-up window, check the entry of your latest version of .NET Framework to enable it and click OK . (What to do if  .NET Framework 3.5 Missing in Windows 10 ?)

After that, reboot your computer and check if this solution works.

About The Author

Position: Columnist

User Comments :

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

SCCM 2107 .NET 4.8 Console crashes on Hierarchy Settings

I have upgraded to SCCM 2107, everything works fine except that Right Click on Site Settings - Hierarchy Management crashes the console and I get a .NET error:

Application: Microsoft.ConfigurationManagement.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.2107.1063.1000, time stamp: 0x904f05b2

Faulting module name: KERNELBASE.dll, version: 10.0.17763.2183, time stamp: 0x12a65345

Exception code: 0xe0434352

Faulting process id: 0x27cc

Faulting application path: D:\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe

The beahvior is consistent on every machine I have the console

.NET installed is 4.8

(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full").Release

I googled the same error on previous SCCM versions it seems the error is back, any idea (except downgrading .NET?)

Windows Server Infrastructure Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications. Infrastructure: A Microsoft solution area focused on providing organizations with a cloud solution that supports their real-world needs and meets evolving regulatory requirements. 516 questions Sign in to follow

Hi @Anonymous

We have a topic with a problem similar to his, I recommend you take a look at it in the link below:

https://social.technet.microsoft.com/Forums/en-US/f9472917-ae56-43c3-8c3f-a3fe7f4d0c19/sccm-1902-console-crashes-when-opening-hierarchy-settings?forum=ConfigMgrCBGeneral

-----------

--If the reply is helpful, please Upvote and Accept as answer--

@Anonymous I experienced the same issue in our environment and the solution was to correct any misconfigurations with the Reporting Services and reinstall the site role. I posted about it here, if it's helpful. https://molloy.rocks/sccm-2107-console-crash/

Hope it helps!

Message: Unhandled Exception has occurred in your application. The document has not been opened.

You may run into this error if a different version of Crystal reports runtime has been installed (typically resulting from an update to your Accounting package and or other application). NOTE: If you're uncomfortable with or would like assistance walking through the steps below please create a support ticket with us and we'll be happy to assist. Steps to modify the MISys.SBM.exe.config file: Note: Make sure to completely close out of all MISys windows (including the MISys login screen) first

• Locate the MISys.SBM.exe.config file. This file is located under your MISys Client install directory (by default C:\Program Files (x86)\MISys\MISys SBM\MISys SBM 6.4 Client).
• Backup the MISys.SBM.exe.config file.
• Open the attached text file MISys-6.4-AppConfig-Block-for-Crystal-Reports-and-Sage-300.txt (at the bottom of this KB Article) and Copy the contents.
• Right click on the MISys.SBM.exe.config file (you located in step 1.) and select edit (which will likely open the file using Notepad).
• In Notepad verify that Word Wrap is disabled by clicking Format (the Word Wrap option should NOT be checked).
• About half way down you'll see a section starting with:<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
• Place your cursor at the end of this line and hit Enter to create a new line below it.
• Right click and select Paste (which should paste the contents of the attached text file).
• Save the changes and exit Notepad. 

Log back into MISys and try printing a report.

NOTE: If you know that you are running the Crystal Reports runtime (SP26) or you still have problems after performing the steps above, repeat the steps but in Step 3. use the text from the attached file MISys-AppConfig-Block-for-Crystal-Reports-SP26.txt (at the bottom of the KB article) .

If you continue to have problems, please create a support ticket with us and we'll be happy to assist.

  « Go back

Contribute to the Windows forum! Click  here  to learn more  💡

May 10, 2024

Contribute to the Windows forum!

Click  here  to learn more  💡

• Search the community and support articles
• Windows Vista
• Search Community member

Ask a new question

Unhandled exception has occurred in your application. Cannot create Activex

Hi, I am hoping someone will help with an issue. 

My friend has an error message everytime they start up their laptop. Windows Vista Home Premium - Service Pack 2 - 32 bit OS - There is no info for RAM and Processor.

They did have issues with installing some updates: Security Update for Microsoft .NET Framework 4 on XP, Server 2003, Vista, Windows 7, Server 2008 x86 (KB2742595) - but I resolved that issue when I used the net frame repair tool.  They still have an issue with Update for Windows Driver Framework version 1.11 for Windows Vista (KB2761494) - Installation date: ‎23/‎03/‎2013 02:58 - Installation status: Failed

Could anyone contact me with a fix please I have several hours on the internet trying to find a resolution.  Many thanks. All details of the script is below.  The pop up message is:

Microsoft .NET Framework

Unhandled exception has occurred in your application. If you click continue the application will ignore this issue and attempt to continue. If you click quit, the application will close immediately.

Cannot create ActiveX component.

Details are below:

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.Exception: Cannot create ActiveX component.

at Microsoft.VisualBasic.Interaction.GetObject(String PathName, String Class)

at Reminder_MUI.Startup.CheckForAdminAccount()

at Reminder_MUI.Startup.Startup_Load(Object eventSender, EventArgs eventArgs)

at System.EventHandler.Invoke(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(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)

************** Loaded Assemblies **************

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.4234 (VistaSP2GDR.050727-4200)

CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

----------------------------------------

Reminder_MUI

Assembly Version: 3.0.1.0

Win32 Version: 3.0.1.0

CodeBase: file:///C:/Applications/OEM/Reminder/Reminder_MUI.exe

Microsoft.VisualBasic

Assembly Version: 8.0.0.0

Win32 Version: 8.0.50727.4016 (NetFxQFE.050727-4000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll

System.Windows.Forms

Win32 Version: 2.0.50727.4236 (VistaSP2GDR.050727-4200)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

Win32 Version: 2.0.50727.4235 (VistaSP2GDR.050727-4200)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

System.Drawing

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

Accessibility

Win32 Version: 2.0.50727.4016 (NetFxQFE.050727-4000)

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

System.Runtime.Remoting

CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

Report abuse

Reported content has been submitted​

1 person found this reply helpful

Was this reply helpful? Yes No

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Thanks for your feedback.

Replies (5) 

Question info.

• Norsk Bokmål
• Ελληνικά
• Русский
• עברית
• العربية
• ไทย
• 한국어
• 中文(简体)
• 中文(繁體)
• 日本語