Hi,
I am currently trying to install Epicor 10.2.200.3 and I’m getting the error below. Anyone know why?
Error: The application server was configured correctly but an error occurred trying to configure the token service : Server is not available. Please review Server Event Logs for details.
Thanks,
What does the server event log say?
Message authentication failed.
Service: net.tcp://edmus12-edev01.mydomain.local/ERP102200/Ice/Lib/TokenService.svc
Action: Ice:Lib:TokenService/TokenServiceSvcContract/AdminSetTokenConfig
ClientIdentity: mydomain\Administrator; S-1-5-21-170147005-2479465307-113789238-500
ActivityId:
FaultException: Server is not available. Please review Server Event Logs for details.
I can`t find any other logs…
Can you connect to app server in admin console? If yes, setup Token settings from there - Configure Token Authentication on the Actions panel.
Hi Olga,
The option is there but grayed out.
That is typically grayed out if the application server is not running. Can you right-click and connect to the running application server? The first message you received when deploying can be ignored.
Reboot the server and check
I wanted to update this thread because I ran into a very similar error today with the Token Service while I was trying to deploy a NEW E10.2.300 AppServer Configuration:
The application server was configured correctly but an error occurred trying to configure the token service: The type initializer for ‘The type initializer for ‘Ice/Extensibility.AppServerEventsHandler’ threw an exception.’ threw an exception.
The application server was configured correctly but an error occurrred trying to configure the token service: The type initializer for ‘The type initializer for ‘Ice/Extensibility.AppServerEventsHandler’ threw an exception.’ threw an exception. —> System.ApplicaitonException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
— End of inner exception stack trace —
at Epicor.ServiceModel.Channels.ImplBase’1.ShouldRethrowNonRetryableException(Exception ex,DataSet[] dataSets)
at Ice.Proxy.BO.UserFileImpl.GetUserFile()
at Epicor.Mfg.Administration.ServerManagement.ApplicationServerManager.Forms.NewSessionForm.BackgroundWorker_DoWork(Object sender, DoWorkEvenArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEvenArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
It would have been nice if the error said, “Hey Dummy, your database is from an older version!”
I was working on a brand NEW install for 10.2.300 on a new VM so naturally I was using the Epicor10_NewInstallGuide_102300.pdf but I had brought over a copy of our E10.1.600 SQL database.
Unless I’m missing it, this guide doesn’t mention that when you add a Database to the Epicor Administration Console, if it is from an older version of Epicor, that you need to right-click on it and choose Upgrade Database to run the Tasks needed to convert your DB from, in my case, ERP101600 to ERP10.2.300.
Side Note: I feel like this is a super “duh” moment for me but in my defense I don’t do this every day and for some reason was thinking that the other Conversions that I would be running would take care of that. I just didn’t think that through well enough and therefore ran into the above error.
Once the upgrade of my database was complete, I was able to successfully Configure the AppServer. Just wanted to post this to save someone time if they run into this error.
What saved my 
was this KB article from EpiCare, thank you @sbosque:
Token Service error Deploying Application Server - KB0041568
To add to the body of knowledge…
I just had a very similar problem but the cause was different. In my case the error was caused by a bad db name in the Application Server configuration. Somehow i had an extra space character in the db name…the Test Connection button returned a positive result but the application server would not start.
Brett
I had the same issue on Friday night. I ended up deleting my app server from the admin console and re-registering them. I’ll keep that KB in mind though. I have to do another install tonight.
Reboot the application server and check
