I am recieving the below error message when I try to log into InfoView and or the CMC. I have restarted the SIA and Tomcat. I have also RDP’d directly onto the server to make sure I can ping the repository and I tested the DSN. I have also tried accessing the CMC and InfoView directly from the servers browser window. Does any know what the error message means and or know possible resolutions?
Error: Server INDSUS134:6400 not found or server may be down (FWM 01003) null
I’ve the same problem, I installed 3.1 version for testing, 2 month ago but I don’t migrate any object by now, and today return to access it, but last log tell me a warning about there is no password, setting username and password as default values, and the same message for authentication type and CMS name.
But I don’t detect any error, the same message appeared in the first log when I installed and was working…
I had the same issue for logging into BusinessObjects (InfoView, CMC, Deski and Designer) which was really puzzling as the server it referred to in the error was up and running (as I was actually RDP’d to it)…
A bit more background on my particular issue: I had recently completed a fresh install of BusinessObjects onto a new vm server as the original installation had multiple issues.
To solve it I logged in to the CCM and it would not let me into ‘Manage Servers’ so I double clicked the SIA, went to ‘startup’ tab and noticed that the Remote CMS Servers had automatically connected to both the new and old servers (seperate entry for each, with same port number : 6400). I then stopped the services (SIA + Tomcat) and navigated back to the startup tab in the SIA and removed both entries under the ‘Remote CMS Servers’. I then started the services again, clicked on to ‘Manage Servers’ and entered the administrator credentials. This allowed me access to the breakdown of services.
The problem here was that it had clustered to the orginal installation automatically (I have been assured nothing was changed without my knowledge) and there was 2 instances of each service (1 for old server and 1 for new server). I basically had to delete the servers that referred to the old server.
Finally did a quick stop/start of the services in the CCM again and logged into InfoView and CMC with no problems.
Hope this helps others in same predicament as this took me ages to resolve but is all working fine now.