Page Server cannot log on to the CMS

[weikfan]

Hi,

Our CE10 is on a Windows 2003 server with the web server on a UNIX machine.

In our CE10 development environment, I get the following message once in a while when View on Demand of a report.

'The Page Server cannot log on to the CMS. This is due to invalid security credentials. Please verify your user ID and password.'

If I View on Demand again right after I close the message window and without doing anything, I am able to run and view the report.

At the time of the error, all services seems to be running - they are all in the 'running' status in CCM.

Could you please let me know what would have caused this?

Thanks.
Fan

 

[synapsevampire]

Sounds like you have an intermittent connection to the web server to me.

Check to log files from both machinesfor more detailed information, on the CE server youshould be able to use the Event Viewer.

-k

 

[weikfan]

Thanks for the quick reply.

The event viewer log shows several occurance of the following warning.

'The failure code from authentication protocol Kerberos was "The attempted logon is invalid. This is either due to a bad username or authentication information. (0xc000006d)'

The warning was listed with LsaSrv as the Source and SPNEGO(Negotiator) as the Category. Could you please let me know if the source and category mean anything? I also don't understand why there are several entries for it since I am one of the 2 users on the system and I am the only one that got this error today.

Around the same time when the warning was generated, there are other warnings related to printer purges from individual PCs.

I can't see any logfiles on the Web server probably because of security. I might need to ask the server administrator to check. Could you please let me know file path for web server?

Thanks.

 

[synapsevampire]

Sounds even more like network issues.

I don't know your network path.

-k

 

[weikfan]

Thanks.

 

[weikfan]

Hi again,

I found more errors in the Event Viewer under Application that seemed to be associated to the error.

Source: Crystal_WebCompServer, Category: Transport
Transport error: Communication failure

Source: Crystal_cacheserver, Category: PageServer
Unable to connect to cluster @WCASD34.CHEMD.NET to retrieve updated CMS member list. Logon cannot continue.

Source: Crystal_cacheserver, Category: Transport
Transport error: Communication failure.

Do you think it is network problems or the CE services are not working with each other properly?

Thanks again.
Fan

 

[Turkbear]

Hi,
For some reason the server(s) cannot find or connect to the CMS database..

Where is it located, what database is used, and do the services run under an account that has full access to it?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[weikfan]

Hi Turkbear,

The CMS database is a Microsoft SQL database and sits on a sql server. The account for the services does have full access to the CMS database.

Our web server is on a UNIX server connected to the application server via the Web connector.

Thanks.
Fan

 

[Turkbear]

Hi,
Any firewall or port restrictions between the Unix and Windows servers?





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[weikfan]

There isn't firewall for our development environment but there is for the production. There is no port restrictions.

For the production environment, the connection drops if no one is using CE for a while. We got a script from Business Objects to run periodically to keep the connection alive.

We found this error logged in both the development and the production environment.

Thanks.

 

[flozee]

Wondered if you have resolved the issue or not. If you have not here is a link to a KB article on BO. Or search the kb article id 'c2016250'.

Hope this helps.

http://technicalsupport.businessobj...sliceId=&dialogID=8670131&stateId=1 0 8668519

I'd like to know if you have done anything different to resolve the issue.

 

[Seabrook7]

We're having the same issues here. One thing BO Support suggested was making sure the CMS and any servers having trouble communicating (causing Tranpsort Warnings) are running under a network account and not the machine system account.

That didn't help us at all.

If anyone has a resolution, please let us know.

Thanks.

 

[weikfan]

I recently found a possible cause for our problem. Our system database server is brought down periodically. When it is brought back up, CMS is started also. But when we start CMS, we probably need to restart all the servers as well even if they are in 'running' status. Maybe they lost connection with the cms database when cms was down.