Application Error 1000 Msvbvm60.dll
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 01 Oct 2016 03:47:23 GMT by s_bd40 (squid/3.5.20)
Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 1000 (Error) Source: Application Error How important is this event? (73 votes) 1 2 3 4 5 not important very important Description This Windows Event does not have a description yet. Add link Text to display: Where should this link go? Add Cancel × Insert code Language Apache http://answers.microsoft.com/en-us/ie/forum/ie8-windows_other/fault-module-name-msvbvm60dll/327159b1-c487-4e28-90ae-b785e68f80f4 AppleScript Awk BASH Batchfile C C++ C# CSS ERB HTML Java JavaScript Lua ObjectiveC PHP Perl Text Powershell Python R Ruby Sass Scala SQL VB.net Vimscript XML YAML Insert Cancel Save Cancel Associated Messages Faulting application winamp.exe, version 5.5.5.2435, time stamp 0x49df8239, faulting module kernel32.dll, version 6.0.6000.16820, time stamp 0x49952034, exception code 0xc0000005, fault https://community.spiceworks.com/windows_event/show/13-application-error-1000 offset 0x0004fcac, process id 0x17d0, application start time 0x01c9f288e4635940.
Jun 22, 2009 message string data: Rtvscan.exe, 10.0.0.359, unknown, 0.0.0.0, 5c737472 Jun 24, 2009 Faulting application svchost.exe, version 5.2.3790.3959, faulting module shell32.dll, version 6.0.3790.4184, fault address 0x0014e84e. Jun 25, 2009 message string data: mmc.exe, 6.0.6001.18000, 47918d09, SqlManager.dll, 2005.90.2047.0, 443f5c4b, c0000005, 00014a2c, 14a8, 01c9f5baaee93ea7 Jun 26, 2009 Faulting application iexplore.exe, version 8.0.6001.18702, faulting module unknown, version 0.0.0.0, fault address 0x027f2c5b. Jun 30, 2009 Faulting application name: firefox.exe, version: 1.9.1.3462, time stamp: 0x4a420bac Faulting module name: NPComponent.dll, version: 1.0.0.3290, time stamp: 0x4a02dbb1 Exception code: 0xc0000005 Fault offset: 0x000056ff Faulting process id: 0x18d0 Faulting application start time: 0x01ca01424fde3a18 Faulting application path: C:\Program Files\Mozilla Firefox\firefox.exe Faulting module path: C:\Program Files\Mozilla Firefox\extensions\{B13721C7-F507-4982-B2E5-502A71474FED}\components\NPComponent.dll Report Id: 9506d56f-6d35-11de-beff-001d603185b8 Jul 10, 2009 Faulting application catstart.exe, version 5.19.3.8333, faulting module catstart.exe, version 5.19.3.8333, fault address 0x0000000000003546. Jul 13, 2009 Faulting application iexplore.exe, version 7.0.5730.13, faulting module ntdll.dll, version 5.1.2600.5755, fault address 0x00011daf. Jul 14, 2009 Faulting application svchost.exe, version 5.2.3790.3959, faulting moduleConstruction and real estate Wholesale Distribution Manufacturing Product quick access: Sage One Sage 50 Accounting Sage 100 ERP Sage 300 ERP Sage ERP X3 Sage HRMS Sage Impact Sage Life Sage Payments Sage Payroll SageCity Site Search Sage City User Site Search Sage https://sagecity.na.sage.com/support_communities/sage500_erp/f/88/t/31612 City User SageCity Home Support Business Partners Accountants Students Town Hall Blogs More ... Sage 500 ERP Sage 500 ERP Installation… Home Forums Blog Training Ideas ACA resources Members More Cancel This group requires membership for participation - click to join Random application errors... three years and counting My original post about these errors was at the old support web-site before this site existed. Imentioned them here in this forum backin this application error 2009post...http://community.sagemas.com/t5/Installation-and-Technical/MAS-500-Desktop-Auto-Shutdown/m-p/5178#M173I'm posting toprovide a status update. The situation is that we never saw any similar errors when our Terminal Server was running Windows 2000. It was not until we installed a Windows 2003R2 Terminal Server a little over three years ago that we began to see these errors. I worked with Sage and our VAR trying to solve them for several months, but eventually we all basically just decided thatwe could not solve application error 1000 themandthat we wouldjust have to live with them. In the back of my mind, though, I had beenhopeful that perhaps some future upgrade would fix them. Well, three years and several upgrades later, I just thought I would update you all...they haven't changed a bit.From the time we started seeing them immediately after upgrading our Terminal Server from Windows 2000 to Windows 2003R2, we have since gone through the following upgrades:7.05 to 7.20.x to 7.30.2 and finally to 7.30.5.Our Dell PowerEdge 1900 Terminal Server was reformatted and rebuilt with Windows 2008 SP2 last summer.And finally a week ago our Dell PowerEdge 2900 SQL Server was reformatted and rebuilt taking it from Win2003R2/SQL2005 up to Win2008R2/SQL2008R2.Our system is now as current as it can possibly be.None of these upgrades have had any effect on the errors. With about 15-20users onthe system per weekday, we continue to average about onerandom application error per day on our Windows 2008 SP2 Terminal Server.All server firmware and drivers are the latest available.I would be interested to know if any of you see similar errors in your Application Event Logs on your PCs (workstations or Terminal Servers) running the MAS 500 client.Here are a few examples of the types of errorsI'm referring to.Log Name: ApplicationSource: Application ErrorEvent ID: 1000Task Category: (100)Level: ErrorKeywords: Classic