Addition : This remedy server is accessible from older version of windows TS server so database is ok.
are you able to connect to the arserver using other clients such as Remedy Administrator, web brower or API driver?
No connection with other Admin tool either. Same result and error message.
if possible I would try to restart the server process and check arerror.log file
Correct me if I'm wrong you are able to connect the AR Server from one of the Server ?
Are you having issues to connect AR Server from only one BOX ?
What is the result if you are try to connect from Mid-Tier ?
If you have connection problem from only one machine please do telnet IP or FQDN PORT [e,g 192.168.1.2 1831] allso do tracert IP and check how your packet is routing to destination server.
Repeat the same steps from other server where you are able to connect ar server. put IP Address and Port instead of DNS Name on ar user / admin account preferences and try to connect the server.
May be network/firewall related issues.
Thanks & Regards,
We have a two servers where it works. These servers were built back in 5 yrs ago. Windows 2003 no SP. We have rebuilt other old servers with Windows 2003 SP2 ( same name and ip as before and in same wlan as other working servers) and from these "new" servers connection dont work. So in the network side route is the same as before so it should not cause any issue.
Telnet, ping , tracert goes ok.
Must say this is a really strange problem.
Cannot get my hands on arrror.log .( no reboot alloved as server is in use. Direct client connections from workstations ( from office lan ) ) We checked general AR- logs and SUN server logs but nothing there that would have catch my eye.
Are you useing Mid-Tier ? if yes
try to connect from Mid-tier ?
Did any changes happen on your environment in recent past. When you have successfully connected last tim ?
Also check the AR process status from solaris console.
ps -ef | grep ar
Open your services list on the client.
Find "Remote Procedure Call (RPC) Locator". Start the service.
Connect to the server.
check the firewall settings windows 2003 if any ports are blocked, check the server name & Sybase server name parameters in ar.conf. restart the workstation service in windows.
There can be many resons for this issue.
1) Check your conf file and see if it is same as the old one
2) Use IP address directly (I mean the numeric value x.x.x.x) instead of the server name.
3) Check if there is an entry of server in host file.
4) Check if your anti viruse is not allowing you to connect to the server
As the connection Refused Error is there, so need to Check whether firewall is blocking any port, or anitivirus is not allowing to connect to server.
Hi...did u find the solution to this problem...I am also facing the same problem while installing ARS 7.6.04 on MS SQL server 2008 R2. I tried installing multiple times but no success..
W2K8 R2 put in a lot of security blocks...go to Windows firewall and allow RPC across the board bi-directional.