.NET Questions and Solutions

Symptoms
This update applies only to Duet client computers and is also known as Hotfix 1 for Duet 1.5 Service Pack 2 (SP2).
Resolution
Issues that this hotfix package fixesFixed incorrect logging of errors that should be warnings. Added logging to identify when Outlook is started with a profile not configured for Duet. During metadata upgrade, increased the time that a user has to close running Office applications to 30 seconds. Improved Client Protocol Handler logging to include BoundItemType, BoundItemId, and CorrelationID values. In a primary or a secondary computer configuration, a metadata upgrade results in an item becoming unbound if it was created on the secondary machine and the Sweeper did not process it yet. Copying and pasting a bound item no longer results in a new bound item. The new item is a standard unbound Outlook item. Improved user feedback if Duet cannot log on to Exchange Server. The Duet add-in for Word no longer automatically loads unless a scenario is installed that needs Word integration. The metadata cache on a client is no longer encrypted. Fixed a scenario in which a Duet utility crashes with a System.NullReferenceException during metadata deployment if calls to the metadata server result in a time-out. Past occurrences of a bound recurring appointment series become unbound during Duet parallel appointment creation. Bound items become unbound if the OBASQLEXPRESS instance becomes unavailable while the Sweeper is running.

Symptoms
In a Remoting scenario, you may try to move the Enumerator for a Hashtable from the server side to the client side. You do this so you can iterate through the Hashtable on the client side. While you are enumerating through the Hashtable, you may receive the following error message:

An unhandled exception of type ‘System.InvalidOperationException’ occurred in mscorlib.dll
Additional information: Collection was modified; enumeration operation may not execute.
Resolution
The error occurs because the Hashtable Enumerator is a MarshalByValue component. Therefore, the Hashtable stores the owner of the Hashtable internally. When you request the Hashtable on the client side, the Hashtable is deserialized on the client side. During deserialization, the internal Hashtable is reconstructed. Therefore, the enumerator fails.

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
FRxReportManager.exe – Common Language Runtime Debugging Services
Application has generated an exception that could not be handled.
Process id=0×400 (1024), Thread id=0×4c4 (1220).
Click OK to terminate the application.Click CANCEL to debug the application.
This error occurs when trying to launch Report Manager that is installed as a network client (thin client).
Resolution
This error will occur when the user has insufficient permissions to the Report Manager directory on the server.

Symptoms
When you build or run a client application (such as a Microsoft Visual C++ application) that runs anSQL statement on a Microsoft Jet data source, the client application may fail with anunhandled exception. You may receive an error message that is similar to thefollowing:

Unknown The error message may also contain the following error code:

0×80040e14 This problem may occur even if theclient application runs a valid SQL statement.
Resolution
This problem occurs because the Microsoft Jet database driver .dll file (Msjtes40.dll) is not correctly registered.