basecamp.exe - ordinal not found

The Required Info

I followed the instructions and got the following...

The Event Viewer for Adminstrative Events listed BaseCamp error events as Event ID 1000 andTask Category (100). There were two views offered.

The General View had...

------------------------------
Faulting application BaseCamp.exe, version 3.1.2.0, time stamp 0x4cdc09cd, faulting module Uè‹‹Mè‹P8ÿÒ‰…, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000138, fault offset 0x00009eed, process id 0x1e50, application start time 0x01cbad8febb6e5e9.
------------------------------

The Detailled View had...

------------------------------
This event is not displayed correctly because the underlying XML is not well formed. Below is the raw text of the event.

100021000x8000000000000037801ApplicationMainBaseCamp.exe3.1.2.04cdc09cdUè‹‹Mè‹P8ÿÒ‰…6.0.6002.1800549e03821c000013800009eed1e5001cbad8febb6e5e9
------------------------------

I also looked back through the kogs for the previous failure, in case the consistency of the message should give you a clue...

------------------------------
Faulting application BaseCamp.exe, version 3.1.2.0, time stamp 0x4cdc09cd, faulting module Uè‹‹Mè‹P8ÿÒ‰…, version 6.0.6002.18005, time stamp 0x49e03821, exception code 0xc0000138, fault offset 0x00009eed, process id 0x1130, application start time 0x01cbac0ab4555189.
------------------------------

The first time I saw this error was 4th Jan. However, I had not run BaseCamp for quite a few (6?) days.

I don't think I installed anything before it failed. Afterwards I think I installed Mozy, but just possibly it was before the 4th. I have been having frequent crashes of WindowsLive.

Hope this helps. I would like to be able to use BaseCamp again!

Regards,

Simon

Thanks for those who help checking the error in the event viewer.

Since the faulting module name "Uè‹‹Mè‹P8ÿÒ‰" is badly corrupted, I suspect its either the .NET framework, or some Windows system files got corrupted (most likely caused by a Windows Update).

Possible solution:
1. Run the .NET Framework Setup Verification Tool and verify each product that is available.

It should be pretty straight forward to use. Here is the user guide just in case.

2. Run SFC (System File Checker). Make sure you run it from the command prompt.

3. If step 1 & 2 fail to identify/fix the problem, then try one of the following:
Plan A, perform a system restore.

Plan B, completely reinstall BaseCamp & .NET Framework
a) uninstall BaseCamp
b) uninstall ALL .NET Framework and hot fix
c) if you have trouble uninstalling .NET Framework, use the .NET Framework Cleanup Tool
d) download and install .NET Framework 3.5 SP1 (which will install 2.0 SP2 and 3.0 SP2 as well)
e) install BaseCamp

Plan C, uninstall recently installed Windows Updates one-by-one and see which one may have caused the problem (you can install them back later on).
a) goto Control Panel -> Uninstall a program (Add or Remove Program for XP) -> View installed updates
b) sort the list by date
c) uninstall the latest Windows Update / .NET Framework hot fix, one at a time
d) try launching BaseCamp
e) repeat step c & d

=================================================
THENOMADS,
Did you run sfc inside command prompt? The command prompt window should remain open after the scan is done.

basecamp.exe - ordinal not found

KFPANDA,
I originally ran SFC from the Start/Run box, but I have now done it from the command prompt (via cmd in the Run panel) with no report offered and the same result with BaseCamp.
I'm not to sure about the setupverifier tool. That's getting in a bit deep for me.
I'll see if I can get some local advice on its use and get back with any results.
Cheers
Ray

I have tried some of this...

Thanks for those who help checking the error in the event viewer.

Since the faulting module name "Uè‹‹Mè‹P8ÿÒ‰" is badly corrupted, I suspect its either the .NET framework, or some Windows system files got corrupted (most likely caused by a Windows Update).

Possible solution:
1. Run the .NET Framework Setup Verification Tool and verify each product that is available.

It should be pretty straight forward to use. Here is the user guide just in case.

This gave the following result...

Process 'Netfx20TestApplication.exe' exited with return code 0

Which I understands means that all is OK with .NET

2. Run SFC (System File Checker). Make sure you run it from the command prompt.

There were multiple problems, of which these were the only two that were not repaired or ignored...

0000014d [SR] Cannot repair member file [l:20{10}]"tcpmon.ini" of Microsoft-Windows-Printing-StandardPortMonitor-TCPMonINI, Version = 6.0.6001.18000

0000016e [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6002.18005

I have not attempted to manually fix them.

3. If step 1 & 2 fail to identify/fix the problem, then try one of the following:
Plan A, perform a system restore.

Don't know that I want to do that just now. Don't recall when I last set a restore point. A long time ago I think (unless it happens automatically).

Plan B, completely reinstall BaseCamp & .NET Framework
a) uninstall BaseCamp
b) uninstall ALL .NET Framework and hot fix
c) if you have trouble uninstalling .NET Framework, use the .NET Framework Cleanup Tool
d) download and install .NET Framework 3.5 SP1 (which will install 2.0 SP2 and 3.0 SP2 as well)
e) install BaseCamp

I am not too enthusiastic about doing that just now.

Plan C, uninstall recently installed Windows Updates one-by-one and see which one may have caused the problem (you can install them back later on).
a) goto Control Panel -> Uninstall a program (Add or Remove Program for XP) -> View installed updates
b) sort the list by date
c) uninstall the latest Windows Update / .NET Framework hot fix, one at a time
d) try launching BaseCamp
e) repeat step c & d

The last update was (I am sure) from a time when BaseCamp was still working...

Kernel-Mode Driver Framework v1.9 (KB970158) on 24/12/2010

Nevertheless, I uninstalled this and rebooted. There was no change in behaviour. (Now, how do I reinstall this update, assuming it is needed?)

(Later edit to this post... just found I installed BaseCamp on 31/12/2010. So definitely not this update.)

Regards,

Simon.

Don't know that I want to do that just now. Don't recall when I last set a restore point. A long time ago I think (unless it happens automatically).

By default, Windows create a restore point when you install new software or Windows updates. You can launch the System Restore wizard just to check and see if there's any checkpoint available without performing a restore.

Nevertheless, I uninstalled this and rebooted. There was no change in behaviour. (Now, how do I reinstall this update, assuming it is needed?)

It will show up in the Windows Update again.

KFPANDA,
I have run the .net setupverifier.
There were 5 .net product versions installed.
1.0, 1.1 SP1, 2.0 SP2, 3.0 SP2 and 3.5 SP1.
All versions were correctly verified.
Ray

Problem can be caused by recent version of avast antivirus. Solution is to revert to earlier version of avast or use beta.

BaseCamp and Avast

Ah, now there is an interesting connection.
I installed Avast on the 2nd or 3rd of Jan.
I'll give it the mirror treatment tomorrow morning.
Thanks POPEJ

Avast user also

I have been using Avast for a long time. I'll see what options I have for adjusting what it does.

You mention beta - beta of BaseCamp or Avast?

Cheers,

Simon.