Export to MS Excel causing failure on nicrptom.exe

[JanelleP]

Folks,

We have created a user defined report based on the agent performance and activity code tables. This was designed in Crystal Reports 8.5 and imported successfully into Symposium.

I am able to run this report, view it and export it to Adobe without any problems. When I attempt to export it, with only 1 days data, to MS Excel, either extended or not extended, it fails and shows the following messages:

"Symposium Call Centre Ops - Report Manager has encountered a problemand needs to close. we are sorry for the inconvenience" I then click on the more info hyperlink and am provided with the following:

Error Signature
AppName: nicrptom.exe
AppVer: 4.0.0.0
ModName: msvcrt.dll
ModVer: 7.0.2600.1106
Offset: 000336d2

and an error report with further detail.

I can export the same results from Crystal Reports to MS Excel. This is only happneing in Symposium.

Does anyone have any idea why this won't export? Is it some settings we have chosen in Symposium or is it related to cache size or something for the specific desktop?

I'm at a loss!

Thanks,
JanelleP

 

[cgilmer]

Symposium is very frustrating when it comes to updateded Drivers. Most of the time I have seen this happen it means that an upgrade or patch was made to Microsoft office(or included application) which updated that dll. Symposium just doesn't work well with others... its almost like it takes a snapshot of them on loading and sees any updates to versions and drivers as some form of incompatibility.

 

[JanelleP]

Thanks CGilmer.

I take it the version of the msvcrt.dll file is the one listed as ModVer, 7.0.2600.1106.

Do you know which driver versions Symposium "plays well" with or is this a question I need to direct to Nortel?

 

[cgilmer]

Honestly I think the reason the Web Client exists is for this very reason. They got tired of supporting and troubleshooting FAT Client instllations.

The only safe way to get symposium to work is to load it to its own computer.

The old culprit used to be the DAO(Database Access Objects) updates that came packaged with Office and Access/Excel. Not sure if its still handled the same.

When I look at the readme file in a Symposium installation I see this text under the DAOMIN folder.

"This setup installs DAO runtime with Jet MDB support only (version 3.0). "

The Driver that I know works for Sybase is the Sybase ASE ODBC Driver 3.5.00.10

You can find the list of the driver versions by going to Control Panel, Administrative tools, ODBC Data Source Administrator, and then go to the Driver Tab.

This will show you the list of all the driver versions that each program uses via the DLL. The fastest and cleanest way to check this out is to find a computer that works and compare it against a computer that doesn't.

 

[cgilmer]

Additionally, on the ODBC DS Administrator page there is a User DSN and System DSN tab.

If you select the Excel Files you can configure it to use older versions of what you have. There should be a "Version" dropdown box.

On the System DSN list you will find that the NICRPT_DSN and Blue are both Microsoft Access Driver listings. You should also be able to see the damage that can be caused by updating the Sybase Drivers to something symposium can't work with if you look at all of the ICCM entries on this list.