Hi,

I've been looking at a similar issue to this one, but am awaiting logs so I can get see the exact cause of the error. For that case, I advised that we should probably be looking at the request timeout settings on the client and server.

In IIS 7.x, you can change the request timeouts in inetmgr. Right-click your web site, then go to Manage Web Site -> Advanced Settings.

The timeout setting is available under the Connection Limits section.

If this doesn’t resolve the issue, then it’s possible that the timeout is happening on the client.

I've had a quick look at the MSDN documention for SoapHTTPClientProtocol, and I can see that there's a Timeout property, but I'm not sure if this uses the default values from the registry.

http://msdn.microsoft.com/en-us/library/system.web.services.protocols.webclientprotocol.timeout(v=vs.71).aspx

So far as I can see the default value is 100 seconds. We can probably try setting the WinINet timeout settings on the client. It might be worthwhile setting this to 5 minutes. You can do this by doing the following:

1: Start Regedit.
2: Locate the following subkey:
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings
3: In this subkey, add a ReceiveTimeout DWORD entry that has a value of ()*1000. So, if we’re setting the timeout to 5 minutes, we can set the value of the ReceiveTimeout entry to 300000.
4: Restart the computer.

If Accpac is running as another user aside from the logged-in user, then you will need to change the setting under their user’s branch of the registry. This will be available under HKEY_USERS. IF this doesn't work, and the timeout is happening because of this timeout property, then a development case will likely need to be raised to set it programatically (assuming there isn't an option in the client application).

If the above doesn't resolve the issue, can you log a case with your local support team please? They'll need to see a full copy of the CRM logs (including the web services logs and IIS logs).

Thanks,
Rob