Symposium Report generation error

[Chandhru]

One of my clinet systems is not able to view/print reports in Symposium. It is giving " There was an error while trying to print Report!. Failed to access information report file".

I checked my report listener, it is running fine. but even then I am not able to print my reports. so I tried to unistall my symposium client. while trying to uninstall I am getting the following error and unable to unistall.

" Internal Error 2330.999
C:\Program Files\Nortel Netowrks\Symposium Call Center Server\client\en\script\samples\Routing-Examples\NSBR_Examples\Primary "

What should I do to fix this issue.

Thanks in advance
Chandhru

 

[MtlSwim]

I am receiving that same error for one of my users, but it is related to his NTaccount, because I have several users using the same symposium user logon credentials and they all work. Still looking for an answer.

 

[lretrievers]

In order to create reports using the Classic Client, the user must have rights to write to the hard drive, as this is where the report is formed before it is displayed on the screen. It sounds like there may be some restrictions on the person's PC or logon that doesn't allow them to do this.

 

[MtlSwim]

I make our users connect via remote desktop connection (Terminal Services) to a PC and then open the symposium application all using the same symposium log on, to run reports.
All the user's are administrators on that machine they are connecting to, so they have full permissions.

This has been working for all. I now have a new user who I have given access to this machine and he is unable to run reports. I created a brand new user, and the new user is unable to run reports as well.

The user is able to run real time dispalys.

 

[MtlSwim]

After trying everything, including making a new NT user, I made a new symposium user and this worked.

 

[cgilmer]

There is a documented patch for 5.0 with issues after upgrading/patching the symposium server which nerfs certain reports for all users except sysadmin. You apply the patch or out and make a "configuration change" to the user like removing agent or supervisor from them and adding it back. Its generally just easier to rebuild them in most cases.

Also that is a key indicator that you don't have all of your client patches on the desktops to match the level of the server. Additionally, you should check the Sybase Driver version to make sure no one has installed something like Microsoft Office on the computer which will generally upgrade the Sybase ODBC drivers on your computer to something more current than symposium.

I think we talked about this a few months ago and someone mentioned the client patch 018C fixed the user issue.