Share
Report
3,157After performing a code deployment (modelstore import), we attempted to update our 2 EP Websites with:
axupdateportal -updateall -websiteurl https://mySite.mydomain.com/Sites/DynamicsAX
With each one having it's own 'mysite' address.
1 of our sites worked perfectly, however, the 2nd site wouldn't allow axupdateportal to run due to this error:
The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:10:00'. ---> The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:10:00'. ---> The read operation failed, see inner exception. ---> The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:10:00'. ---> An existing connection was forcibly closed by the remote host
Now this site is unique in that it doesn't use Windows Authentication and instead uses Claims Based. However, we've never seen this error before. When we navigate to the site we see:
At the very bottom when you show the detailed compiler output, I think that it lists all the 'Proxies' from that proxies folder with the same error:
error CS0234: The Type or namespace name 'AX' does not exist in the namespace 'Microsoft.Dynamics' (are you missing an assembly reference?)
It seems like we need to regenerate our proxies, however, we can't due to the socket connection error above.
*This post is locked for comments
I have the same question (0)
All responses (
Answers (
