Suddenly can't connect to server using Admin console

When I open the admin console and click on any of our instances it tries connecting but after a bit fails and returns this error,

"The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+msbin1+deflate). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '

Cannot open database "E11Prod" requested by the login. The login failed.
Login failed for user 'IKICORP\svc.epicor'. body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Consolas","Lucida Console",Monospace;font-size:11pt;margin:0;padding:0.5em;line-height:14pt} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weigh'."

Error returns when trying to connect to any server.

Epicor runs as normal but performance is slower than normal. No changes or updates to server or machine have been performed that I’m aware of. We went live 18 months ago and this just started yesterday.
I do have a support case in with Epicor on this but looking for others who might have seen this.
Has anyone had an error like this?

1 Like

Looks like a login failure from SQL.

2 Likes

Open up the App server config and check the second and third tabs. Those users must exist in the SQL DB and the UI - and their passwords must match what’s in the Appserver config.

Sometimes the UI user will have an expired or changed password by mistake, or the same may have happened with the SQL user.

Get the users and passwords in synch with the Appsever config and set them to never change/never expire - and NEVER let anyone(human) use them for anything.

2 Likes

Interesting. I can log into SQL and connect OK.

That’s a good start. Are you sure that password you used is the one the Appserver config is set to?

Then check the third tab - that user/password is how the Admin Console connects to the UI - just like a user does with the UI.

So something weird has happened. We use a service account for our server, SVC.Epicor. I checked the application server config (for Test and Train right now) I can update the admin console settings (third tab) user and password but it won’t save, or deploy. I get an error saying my SVC.Epicor login is invalid.
image
This has never happened before and the login is valid and no one has changed the password.

1 Like

I’m logged into SQL server management studio and connected to the server using that log in. I’m waiting until end of business and everyone is logged out. Epicor support has advised to stop/start the app pool then recycle the IIS app pool. I have my doubts but will try it.

Yeah, that didn’t work. Waiting on more info from epicor support.

Did you look at the account in AD? I had something like this years ago and the OU of the service account got moved and threw the server into a fit. IT renamed the service account and tried to make the original one again back in the original OU which just made it worse, so I just had them make a completely different service account and started over.

3 Likes

SQL security is two levels deep - first is the server login. Your statement says that works. Second is the user mapping to the database - and the permissions it has. If you can log into the server and then open a query window for E11Train, that’s a start. Then make sure you can alter data to prove the permissions are mapped correctly.

Also, like @gpayne’s response, inside SQL the server login and the DB user mapping can become orphaned, although they look the same. That might be the problem, but it will be evident if you cannot access the database even though you can log into the server.

At this point, given what your experiencing, I’d start with a new service user altogether (like @gpayne mentioned). It’ll get you past this and functioning. You can explore the actual problem later.

3 Likes

So I’ve done some testing and I can connect to any of the databases in SQL and query and make changes to the data with set or update functions with no issues.
All of our instances of Epicor function as normal, everyone can log in and do business as usual. It does seem performance is down a little but not dramatically.
For the last 18 months there have been no issues with the EAC and I’ve done backups and regenerated the databases and stuff like that. This issue just popped up yesterday after I went to investigate the performance concerns.
Epicor support just asked for screenshots of the app server config screens. Hopefully they’ll find the problem.

OK, long story short. We use a 3rd party IT service to maintain our servers and server software and apparently the SVC.Epicor login we use had a password expiration (date?) and so the login stopped for the admin console. Got everything reset and no expirations for any logins.

2 Likes

That was my first thought

1 Like