These steps should be performed by an IT specialist or someone familiar with your server.
There are times when Amicus Server Service shows as Running however no users can log into Amicus Attorney.
When logging into Amicus Attorney on any PC, including the server, if the message appears: “Your Workstation is unable to connect with your Amicus Server.” and when the Show Details is selected the message appears: “Failed to connect to an IPC Port. The system could not find the file specified.” follow the steps outlined below.
CAUSE: This typically occurs after the Server has been restarted. Amicus Attorney uses a specific Port to connect to the Amicus Application Server. Upon restarting the server another application may take that port, preventing Amicus from connecting.
Resolution:
From the Amicus Application Server, confirm the Amicus Server Service shows as Running within the services.
- To access the services on the server, hold the Windows key + R, to open the run command, type services.msc then click the OK button.
- If the Amicus Server Service isn’t Running, select it and click the "Start the service" on the left.
- If the service is listed as Running, however no staff can log into Amicus Attorney, highlight the service and select "Restart the service" on the left.
- Once Started/Restarted, test the login to confirm if firm members can log into Amicus Attorney.
If the previous steps did not resolve the issue continue with the following.
- Confirm the TCP Port Amicus Attorney uses, from the Amicus Application Server.
- Hold the Windows key + R, to open the run command, type regedit and click the OK button.
- Expand Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\AbacusNext\.
- Select Amicus Attorney and the details of this Key will display on the right.
- Locate the TCPServerPort key. On the right, it will show a number in brackets which is the Port Amicus Attorney is using.
E.G.: (49259). Port 49259 is the default port used by Amicus Attorney unless otherwise specified within the application for a Preferred Port.
- Confirm the port is listening, and if another application is using the required Amicus Attorney port.
- Hold the Windows key + R, to open the run command, type cmd and click the OK button to open the Windows Command Prompt.
- Type the following, replacing the number at the end with the number found in Step 1: netstat -aon | findstr 49259
- The screenshot shows what the command and results should look like. Both the TCP and UDP is assigned to the same PID (last column). The problem arises when another process is using the same port for the TCP as noted in the screenshot below.
- Determined what application is using the same port as Amicus via one of the two following methods.
Method 1: While in the command prompt type the next line, entering the PID found in the previous step as noted in the red box.
tasklist /FI “PID eq {id found above}”
Method 2: Open the Task Manager then select the Details screen. To sort by the PID column, click the word PID on the top and the arrow will appear. Locate the PID matching the one found in the previous steps. If it isn’t the AmicusAttorney.XOL.ServerService.exe it will need to be ended to allow Amicus Attorney to resume working.
Prior to the next step it may be simplest to have the server restarted. IF this doesn't address the issue proceed with the next step.
- To end the non Amicus process, select the process, then right click on that process and select End Task. Once ended restart the Amicus Server Service and the Amicus DailyCheck Service, then test the Amicus Attorney by CARET login on the server.
IMPORTANT:
- Do not End task on any crucial processes such as DNS.
- It is recommended to confirm the process being ended isn’t in use as this will kick staff out of the program.
- If the other program being ended is required by staff for their day-to-day work, the application must be manually restarted.
Comments
0 comments
Please sign in to leave a comment.