Sage CRM

IIS & Sage 100 user password. Is there a link I am unaware of? A registry setting? CRM 2018 R2 integrated with Sage 100 Advanced 2018 PU3. Our partner Sage 100 user was in the CRM settings in Sage 100, we changed the password, & all of CRM stopped. I understand why the integration stopped, so I created a ""CRM"" Sage 100 user, used the old password, & put that user in CRM settings & could again Load CRM Data from Sage 100. However, still couldn't log into CRM; just keeps ""waiting on server"" or gets login page & gets to ""almost there..."" & hangs. So, after extensive testing, if I put the old Sage 100 user password back & reset IIS, it works. If I change the password, reset IIS, IIS will not start back up. I can now repeat it on demand, so I have our original user back on its original password in Sage 100. Why?!? Why does IIS care what my original Sage 100 user name & password is?

@PeterWolf

Checking with my team.

Here's a quick thought / question back from the team: I would check if IIS or a CRM app pool is using a domain credentials. Sounds to me that Sage 100 is using network authentication and if it's the same user/password it would affect IIS.

The IIS app pools & all the sites are using a specific domain user with a non-expiring password, due to permission issues, that is different than IUSR or a local account. However, Sage 100 is not using network authentication. I am resetting the password inside Sage 100 & not any domain user or password. The user I am logged into the domain with & the IIS domain user are not the same & not the same username as the Sage 100 user.

Dana, are you still jammed up on this issue? I'm wondering if you reached out to Sage yet? With the holidays and the time of year, I'm down two tech support people so my team is stretched a bit. If Sage has been no help, I can escalate it internally with my team for you. I'm not on here often so hit me up at pwolf@azamba.com if you would like me to do that.

I have reached out to Sage; they wanted to reinstall program files & IIS aliases, but was not sure that was the fix. I am not stuck at the moment because I put our password back, but I will need to get it sorted out at some point.