-
1
- #1
This is for some of you which may be having this same issue. I hope this helps someone have a slightly less stressful day than what I had while dealing with this.
I had the problem where when anyone refreshes a report being viewed via the web component server they were immediately prompted for a login and password. It had in the dialog box the server and database which it was trying to connect to (ODBC) but the server was wrong. The server field was identical to the database field. No matter which login and password was tried, it would never connect to the ODBC. I remotely logged into the web server (Terminal Service) and was able to open the report vis Crystal Reports and refresh the data successfully. I checked the ODBC connections and everything worked,...it just wouldn't work when accessed via the WCS - even if I were loading it from the web server directly. I even updated the p2s0dbc.dll as well as registry entries (article #C2007581). Still not working. I say all this to come to this point....CHECK THE SEAGATE PAGE SERVER SERVICE!!! I changed the "log on as" setting, then stopped and restarted the service. Finally it works. ::sigh::
..just my two cents...
~Bill Powell
I had the problem where when anyone refreshes a report being viewed via the web component server they were immediately prompted for a login and password. It had in the dialog box the server and database which it was trying to connect to (ODBC) but the server was wrong. The server field was identical to the database field. No matter which login and password was tried, it would never connect to the ODBC. I remotely logged into the web server (Terminal Service) and was able to open the report vis Crystal Reports and refresh the data successfully. I checked the ODBC connections and everything worked,...it just wouldn't work when accessed via the WCS - even if I were loading it from the web server directly. I even updated the p2s0dbc.dll as well as registry entries (article #C2007581). Still not working. I say all this to come to this point....CHECK THE SEAGATE PAGE SERVER SERVICE!!! I changed the "log on as" setting, then stopped and restarted the service. Finally it works. ::sigh::
..just my two cents...
~Bill Powell