.NET Questions and Solutions

Symptoms
When a client is linked with the proxy DLL that the Soapsuds tool (Soapsuds.exe) generates, the client throws a remoting exception atrun time. You may receive an error message that is similar to thefollowing error message:

Unhandled Exception: System.Runtime.Remoting.RemotingException:Permission denied for activating type soap:TestClass,http://schemas.microsoft.com/clr/nsassem/EchoExeTest/ServerExe%2C%20Version%3D0.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3Dnull.Server stack trace: atSystem.Runtime.Remoting.Activation.ActivationListener.Activate(IConstructionCallMessagectorMsg) atSystem.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(MethodBasemb, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext,Object[]& outArgs) atSystem.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessagemsg, Int32 methodPtr, Boolean fExecuteInContext)
Resolution
To work around this problem by linking the client, followthese steps:Run the Remoting Server application, and then generate theproxy by using the following command:

soapsuds -url:<ServerUrl?wsdl> -oa:serverexe.dllRun the remoting server.Generate the proxy code by using the following command:

soapsuds -url:<ServerUrl?wsdl> -gcOpen the .cs file that Soapsuds.exe generates,remove the SoapType attribute from the class, and then build the proxy.Link the proxy to the client, and then runSoapsuds.exe.
Note If the remoting server is not running, Soapsuds.exe generates anerror and does not generate the proxy code.

Symptoms
The SNA Server stops responding (hangs) and Appletalk client computers areunable to attain session connections. In the Event Viewer, the followingapplication events appear:

Event ID: 624
Source: SNADUMP.LOG
Description: A process SNABASE.EXE ended abnormally due to a protectionviolation, or similar condition.
Event ID: 4097
Source: Dr. Watson Log
This application, SNABASE.DBG generated an applicaiton error. The error
occurred on <date>. The exception generated was C0000005 at address <address>.A portion of the DRWTSN32.LOG file states the following:

App: snabase.DBG (pid=160)When: <date> @ <time>Exception number: c0000005 (access violation) NOTE: Your DRWTSN32.LOG file will appear somewhat different than thisexample.
Resolution
The SNAAT.DLL send routine is not checking to see if the L-Table is alreadyin a closing state. Therefore, it tries to access its pending queue, whichhas been released. This causes the application exception in SNABASE.EXE.

Symptoms
If the SnaNetMn service is configured for automatic startup in ControlPanel/Services or if it is started manually, the following popup errormessage is displayed:

SNA Server – ERROR # 03…OK Note: This message will not appear in the application event log.
In addition, an application exception in Snanmvt.exe occurs that generatesa Dr. Watson log in the Windows NT directory. The entry created in theDrwtsn32.log file will be similar to the following:

Application exception occurred:App: exe\snanmvt.dbg (pid=<pid #>)When: <date> @ <time>Exception number: c0000005 (access violation)function: sepdnmsd_int[...]FAULT ->67241535 803a00cmpbyte ptr [edx],0×0[...] The following messages will be logged in the Windows NT Application Eventlog:

Event ID: 4097Source: DrWatsonDescription: The application, exe\snanmvt.dbg, generated an applicationerror. The error occurred on<date> @<time>. The exception generatedwas c0000005 at address 67241535 (sepdnmsd_int)Event ID: 624Source: SNA ServerDescription: Creating dump file <snaroot>\traces\snadump.log forsnanmvt.exe
Resolution
The application exception occurs because a corrupted buffer caused stackcorruption while attempting to display popup errors that contained longerror messages. The error message that results from starting the SnaNetMnservice contains a long description, which is why the application exceptionoccurs.
Note: Other errors may result in an application exception when a popuperror message is being displayed. These application exceptions may bereported against components other than Snanmvt.exe.

Symptoms
When you install Microsoft Windows 98 or Windows Millennium Edition (Me), you may receive one of the following error messages when your computer first restarts during Setup:

MPREXE.EXE caused an exception 03H in module USER32.DLL at <memory address>

USR32.EXE caused an exception 03H in module USER32.DLL at <memory address>
Resolution
This behavior can occur if a program, for example an anti-virus software program, is running that prevents Windows from upgrading files on your computer.