Created On: 21 October 2010
Problem:
When trying to install a version a Net Express 5.0 or 5.1, the install reports the error:
Execution error: file " error code: 144, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11)
But then the installation appears to finish alright.
The same error can also occur when trying to start the Net Express IDE.
Execution error: file " error code: 144, pc=0, call=1, seg=0 114 Attempt to access item beyond bounds of memory (Signal 11)
But then the installation appears to finish alright.
The same error can also occur when trying to start the Net Express IDE.
Resolution:
This error can happen if they have a Source Code Control System installed and it is not setup properly.
The installation looks in the registry to find out the location of the Source Code Control interface DLL.
It will then try to load it and initialize it.
It is this initialization that is failing and it causes the IDE to display the reported error.
If they are using the Source Code Control System installed, then the DLL supporting the Microsoft Common Source Code Control Interface isn’t working.
This is most likely because the Source Code Control System hasn’t been setup for operation, eg. environment variables etc.
The registry entries can be removed or renamed until the Source Code Control System is set up to avoid this problem.
Use regedit from a command prompt and either remove or rename the following two entries:
HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider
- contains the currently active SCC provider interface API module location
HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider\\InstalledSCCProviders
- contains all installed SCC providers offering the interface API.
The installation looks in the registry to find out the location of the Source Code Control interface DLL.
It will then try to load it and initialize it.
It is this initialization that is failing and it causes the IDE to display the reported error.
If they are using the Source Code Control System installed, then the DLL supporting the Microsoft Common Source Code Control Interface isn’t working.
This is most likely because the Source Code Control System hasn’t been setup for operation, eg. environment variables etc.
The registry entries can be removed or renamed until the Source Code Control System is set up to avoid this problem.
Use regedit from a command prompt and either remove or rename the following two entries:
HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider
- contains the currently active SCC provider interface API module location
HKEY_LOCAL_MACHINE\\SOFTWARE\\SourceCodeControlProvider\\InstalledSCCProviders
- contains all installed SCC providers offering the interface API.
Incident #2481588
Old KB# 32170
