I have a user that shuts down her computer every night. When she starts up in the morning and tries to connect to AX she gets the error about not being able to connect. I run the AX32.exe as admin and am able to connect just fine. She tries again immediately after and can still not connect. She waits a little while (maybe 30 minutes) and then suddenly she can connect.
I deleted her user in AX and re-imported her. That fixed it for that day. The next day she again could not connect till almost an hour after starting her computer.
Today, she cannot run reports that she ran just fine yesterday. She is getting an error that says:
The request failed with HTTP status 401: Unauthorized
I’m not sure what is going on. I have checked and she does have the correct roles to view and run the reports. And she is a user who should be able to log in without problems.
Does anyone have any thoughts?
I would start by checking event logs in the client machine. Then Active Directory logs, because it sounds to me like a problem with AD. You can also check whether there aren’t unexpected users sessions in AX.
By the way, please ask questions like this in the technical forum, not the developer forum (I’ve already moved this one for you).
Sorry about asking in the wrong forum, thanks for moving it for me.
I have pulled some event logs, but they don’t really tell me much just that there was an appcrash. I cannot find any reason why it crashed. It seems to randomly decide that it cannot connect to the AOS server, even though everything else on the computer is working.
I have checked with her AD account and nothing has changed recently, not even her password. She last changed her password about a month before this started happening, so I’m pretty sure that isn’t connected.
I did find that once when she could not connect to the AOS she had a couple of sessions hanging open when I closed them she was able to connect again. That has only happened once and her not being able to connect is an almost daily occurrence.
I have finally gotten this figured out. We ended up with 2 users who were both getting this same message, but for different reasons. One was easy she just needed to update her password because it expired but she hadn’t logged out of her computer so didn’t notice.
The other user’s computer had picked up a new IP address, but her DNS host file was registered with a different IP. Someone at sometime before I started here had entered it manually instead of letting the computer register itself on the domain and this is what caused the problem.
Thankfully it ended up not being an AX issue and I was able to just delete the entry and tell her computer to register.
I have finally gotten this figured out. We ended up with 2 users who were both getting this same message, but for different reasons. One was easy she just needed to update her password because it expired but she hadn’t logged out of her computer so didn’t notice.
The other user’s computer had picked up a new IP address, but her DNS host file was registered with a different IP. Someone at sometime before I started here had entered it manually instead of letting the computer register itself on the domain and this is what caused the problem.
Thankfully it ended up not being an AX issue and I was able to just delete the entry and tell her computer to register.