Autodesk Desktop Connector Error Code 400

[vince.demino]

Hello,

I am having issues with the desktop connector successfully linking my files.  I currently use the connector to live link my subs files in Navisworks for BIM coordination.  The past two days I have been getting this error message. Upload error. Code: 400 Message: Configuration system failed to initialize.  Both DWG files that have been posted from the subs and my NWC files are not communicating from the site to the desktop connector.  I have tried shutting down the connector as well as reinstalling and nothing has resolved this issue.  Thanks for the help.

Regards,

Vince 

[mespaillat]

Hello @vince.demino,

Thank you for posting to our forums.

Prior to the last two days, were you having any issues with both DWG files that have been posted from the subs (and your NWC file) communicating from the site to the desktop connector.?  If you have re-installed the Desktop Connector, is the installed version 4.1.0.443? If it is not, can you please Check for Updates to the Desktop Connector to make sure you are on the latest version? If updating to the latest version of the Desktop Connector does not resolve the issue, please see below.

The Desktop Connector does collect Diagnostic Logs data which can be used to investigate potential causes for the Upload error. Code: 400 Message: Configuration system failed to initialize message. The log data is output in ZIP format and contains several logs and configuration files. To generate your Diagnostic Logs, please:

1. Go to, and left-click the Desktop Connector system tray icon
2. Click Help
3. Click Diagnostic Logs
4. Once the logs are generated, click the Open File Location button to access your logs

From here you have the choice of inspecting the log files for errors or warnings that you can share with me, or you can share them privately (PM with me for review). To view them yourself, you can extract the folder anywhere on your PC, then look for a folder named EventLogs. Look for a log named ADSKCDX.evtx. This log opens in Windows Event Viewer, and is very helpful in tracking down errors or their likely causes. You can potentially identify the exact issue/error by filtering of the times, and days you were receiving the 400 error codes.

In the example below, it shows an error message that reads:

Comet.Server.Core.Exceptions.ProviderException: Failed to get items by paths for provider BIM 360 Team.
Internet connectivity may have been lost.
An error occurred while sending the request. ---> System.Exception: An error occurred while sending the request. 

If I scroll down to the bottom, it will provide additional information about the error that may identify the likely cause. In my case, these errors were generated due periodic loss of WiFi connectivity. This is further supported bu the InternetCallFailure=true flag. To go a step further, look for a section labeled as == DATA ========================, this is what it reads for the error in my example:

== DATA ========================
ExArg0=BIM 360 Team
FullExceptionToString=System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An established connection was aborted by the software in your host machine. ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine
at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)
--- End of inner exception stack trace ---

I don't expect you to do this yourself, and will gladly help you track down why the error code 400 is being generated. If my hunch is correct, we are most likely dealing with an HTTP error. If the error number (400) is any indication, the connection(s) between BIM 360 Team + Desktop Connector is being dropped on one or both ends (client and/or sever). Lets have a look a the log first to be sure.

Please review this response, and advise if you are able to locate any information in the log that would help us resolve this issue for you. If this response was enough to help you track down and resolve the issue, please click the ACCEPT AS RESPONSE button. If not, lets continue working until the matter is resolved for you.

Thank you for choosing Autodesk.

Regards,

mespaillat

Autodesk Support Team.

[vince.demino]

Mespaillat,

I was not experiencing any issues prior to this week.  I just checked and the app is up to date with the installed version 4.1.0.443.  I am sending you my diagnostic log now. 

Thanks, 

Vince 

[mespaillat]

Hello Vince,

I appreciate the response. Would you kindly include an approximate time/date for the events that were specific to the 400 error codes?

Thank you for choosing Autodesk.

Regards,

mespaillat

Autodesk Support Team.

[vince.demino]

Mespaillat,

I started experiencing the Error code Tuesday morning 3/6 at approximately  7am.

Thanks,

Vince

[mespaillat]

Hello @vince.demino,

I submitted your Desktop Connector logs to the team, but was asked if you could provide the workflow/steps you go through to link and upload the files? You are welcome to record a Screencast, and share the link if it is easier than typing. If at all possible, could you also share the files you are using for troubleshooting? You can upload them to your A360 Drive, and share the links(s) with me via PM.

Please advise.

Thank you for choosing Autodesk.

Regards,

mespaillat.

Autodesk Support Team

[vince.demino]

mespaillat,

I append the subs coordination files (dwg) directly though the BIM 360 Team drive located under "This PC".  Once the path is set, it will update everytime I reopen the NWF coordination file.  When the NWF is reropened, new NWC's are created and upload directly to BIM 360 Team.

Thanks,

Vince  

[mespaillat]

Hello @vince.demino,

I have provided the diagnostic logs to the Desktop Connector team to review. I will update this thread with any feedback I receive.

We appreciate your patience, and apologize for the inconvenience.

Thank you for choosing Autodesk.

Regards,

mespaillat.

Autodesk Support Team

[mespaillat · Accepted solution]

Hello @vince.demino,

I am glad to hear that updating the Desktop Connector from version to 4.1.0.443 to the latest version (5.0.0.593) resolved this issue for you. It was a pleasure working with you.

Please click the ACCEPT AS SOLUTION button to help other community members who may be affected by this.

Thank you for choosing Autodesk!

Regards,

mespaillat

Autodesk Support Team