DirectoryNotFoundException using ETO Server R2
1. If you get a System.IO.DirectoryNotFoundException when using ETO Server 2013 R2. Check to see if this directory exists:
C:\Users\InventorETOServices\Documents\Inventor Server x64 Inventor ETO Server
Note: If the InventorETOServices user has been deleted and recreated, there may be multiple user directories for it, such as:
C:\users\InventorETOServices.<MachineName>.000\Documents\Inventor Server x64 Inventor ETO Server
C:\users\InventorETOServices.<MachineName>.001\Documents\Inventor Server x64 Inventor ETO Server
In this case, add the directory in the newest one. This issue has been reported to Autodesk Engineering.
After installing ETO 2013 Server R2 - cannot establish a client connection.
The start of the error message is:
”The message with Action 'http://www.autodesk.com/IntentServices/2012/02/IIntentServices/SetInteger' cannot be processed at the receiver, due to a ContractFilter mismatch at the EndpointDispatcher”.
This happens when there is a mismatch between the contract used by the client and the contract used by the server. In this case the server is R2 but the client is using the R1 contracts ('http://www.autodesk.com/IntentServices/2012/02/IIntentServices').
This can happen when the client project is being built with ETO Series 2013 R1 but trying to target ETO Server 2013 R2. Generally the version of Series used when building the client project should match the version of Server targeted. The solution is to update the reference to Autodesk.Intent.Services.dll in the client project so it is the same version the server is using. This can be done by installing ETO Series 2013 R2 if it’s not already installed, removing the reference, and re-adding the reference by browsing to the “<Series 2013 R2 install>\Bin\Public Assemblies” directory.
An alternative, in this case, since ETO Server is on the same machine as the client is to update the reference to the Autodesk.Intent.Services.dll to point to the one in the ETO Server Bin directory.
Quickly narrow down the location of a crash.
In one case a crash was occurring in a custom dll. It looked like it was an ETO specific problem. By using IntentTracer to determine the Part/Design and “%%iv_message()” we were able to narrow down the location of the crash which was occurring somewhere in the custom dll. The help toipic for IntentTracer is here:
After finding the design you can use a message box style technique to further narrow down the place of a crash.
%%iv_message("Tracing777Before", show := true)
Call to custom dll was here.
The crash occurred before this message was displayed.
%%iv_message("Tracing777After", show := true)
Note: ETO 2013 R2 allows you to debug rules in Visual Studio
Sphere Design fails after install R2 Hotfix (build 202)
To resolve this problem download this iks file and put it in this directory. (Back up the existing xxhostSphere.iks)
“C:\Program Files\Autodesk\Inventor ETO Components 2013\Library\Inventor\ivhostlib”