Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem running reports on Sympsoium Client

Status
Not open for further replies.

pacojonezl40

Technical User
Oct 22, 2007
45
US
I just inherited a site where I am having an issue running reports on my client pc. I get an error stating "There was an error while trying to print report !Failed to access information from report file."
I am wondering is this a network error, or something as simple as just missing a PeP. My server is running SCCS 4.02.06 with NS040206DP1301S and NS040206SU13S. The Client pc has Version 4.0 (Build 04.01.07) with NS040107SU12C and NS040107G015C.

I have searched the PeP library and found new update SU14S. In the readme under fixes, there is the following :
Q00640094 MAS: R4.2 - Error when activating a Report schedule
Could this be related to my issue?
 
Check to ensure that the server has a printer installed
 
I'm trying to run reports from the SMI Workbench on my Client, not the server.
 
SCCS FAT client 4.0 cannot open any report

--------------------------------------------------------------------------------

Problem Description

Fact:
SCCS
Symposium Call Center Server
SCCS 5.0
SCCS FAT Client

Symptom:
Cannot open reports
Can't run reports
Error: There was an error while trying to print report
THERE WAS AN ERROR WHILE TRYING TO PRINT REPORT! FAILED TO ACCESS INFORMATION FROM REPORT FILE


Change:
New SCCS install.


Cause:
NIC binding order incorrect




Problem Resolution

Fix:
As per SCCS 5.0 Installation and Maintenance Guide, configure NIC binding order so that the CLAN is first, ELAN second. (WARNING - SCCS application must be shutdown first.)
 
are you pulling up reports from your desktop? best bet is to file sent to a folder then do the print.. printing from the server to a network printer is usually a printer path problem. if you can print a simple txt from the server to that printer. then you might need to either repost in symposium or bump this one up to nortel.. magna's post is right IF you can not pull reports up.. if that order was reversed he nailed the problem.. to rule that out, pick a report, right click and run now.. if that works it's running reports, so that side (elan/clan/report listener) is working

john poole
bellsouth business
columbia,sc
 
I checked and the order is correct. CLAN first and then ELAN. Should I just go ahead with the new PePs and see if it fixes?
 
If the PEPs dont fix it, last time I had this happen I just reinstalled the client and all PEP's. I first uninstalled all of the components of the client, including the database driver, etc.

Matt H. - Field Svc Engineer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top