Problems Switching from Oracle to MSSQL

[meismike]

Hey guys, first post and looking for some help.

At my company we currently develop our reports using CR 8.5 and utilize Enterprise 8 to distribute the reports. Our current initiative was to change DB platforms from Oracle to MSSQL and now that we have gone live with the change we are experiencing report server lockups.

In the Oracle world we used "Oracle Server" as the connection type when pointing reports to the DB, for MSSQL we are using OLE DB (Microsoft OLE DB Provider for SQL Server) connection because during testing the MS SQL Server connection changes some datatypes on the actual report.

Since we've gone live the server has become unresponsive twice, needing the PageServer service to be restarted or a box reboot. This is the same physical server we were using for Oracle and nothing has been changed on it. This problem was never evident before. If anyone has any idea why this might be occouring it would be a great help.

Thanks,
Mike

 

[smcnulty2000]

It sounds like you are experiencing an increased load issue whether this is caused by the Oracle to MS-SQL or not. It is possible that the old way of doing things pushed more processing to the Oracle server and put less of the burden on Crystal and the new way is pushing some limit.

There is a microsoft KB article that might help.
It has a pretty long URL from where I'm sitting, so I'll give you the altavista page to find it.

http://www.altavista.com/web/results?itag=ody&q=+"PageServer+service"+&kgs=1&kls=0

In essence, it suggests you reconfigure one or both of the following:



Reconfigure the Crystal Page Server

1.
On the Start menu, point to Programs, point to Crystal Enterprise 9, and click Crystal Configuration Manager.

2.
Stop the Crystal Page Server.

3.
Right-click the Crystal Page Server, click Properties, and check the Command field.

4.
In the Command field, if "-maxDBResultRecords 0" doesn't exist, add to the end of the command text:

-maxDBResultRecords 0

5.
Start the Crystal PageServer.


Increase the Web.config timeout value

If the previous method doesn't work, then you can extend the timeout value in the Web.config file located in the \inetpub\

http://wwwroot

folder. The default timeout value is 90 seconds.

This example increases the timeout value to 10 minutes (600 seconds) without affecting the timeout values associated with either the Microsoft CRM Web application or other .NET applications running on the Microsoft CRM Server computer.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<httpRuntime executionTimeout="600"/>
</system.web>
</configuration>



That's a direct quote, so blame them if it breaks your machine.

Good luck with that.

scott.