SCCS 4.2 Fat Client scheduled reports error

[telebub]

I have an SCCS 4.2 with SWC 4.5. With all of the client's network security in place, scheduled reports to a file will not go across the network to the client PC when using the web client. I thought I could get around that by loading Classic (Fat) Client S/W onto the client PC. The S/W loaded successfully. It is patched successfully. I can create and schedule the reports to a file on the local PC and activate them. If I look at the scheduler I see my reports and they look like they are ready to go. Once the scheduled time passes the scheduler shows them ready to run for the next scheduled time but there is no report in the directory I created.

I get an error in the event viewer 46213 stating a Client/server communication error. I can run the report manually and export it to a file with no problem. Can anyone shed some light on this or has anyone come across this before? Could the network security issue I have with the web client also be in play with the FAT Client?

War Eagle!
Lions Baseball '09!

 

[sandyml]

Concerning the fat client. You need to ensure that Report Listener is running in order for the scheduled report to run. That means that if the user logs off their pc, the report won't run.

Why don't you create a shared folder on your SWC server and have the SWC export reports to that folder?

 

[captaingadget]

I agree with sandyml, it's really bad idea exporting a scheduled report to a users PC. Map a drive from the users PC to a shared folder on the SWC so that they go and fetch the reports.

 

[Milesprower]

I agree with those above, web client is the way to go.

However, if you do need to used classic client, make sure your DNS settings are correct. When SCCS goes to run a scheduled report to a classic client, it uses the name of the PC, not the IP. If your company dynamically assigns IP's (almost everyone does, these days), the DNS settings for your organization need to be up to date (so the SCCS can find the client where the report is scheduled to print). The PC must be on with Report listener running for the report to print successfully.

 

[telebub]

Thank you all for the replies. I agree with all that SWC is the way to go but as stated in my initial post, the Corporate Security of this organization will not allow mapped drives across domains.

Milesprower, I agree and think we have DNS issues.

Just to let you know why I am attempting this: A supervisor currently runs 32 Agent Performance reports to a printer every morning. These are daily reports, 1 for each agent. She then runs an App Performance report, makes 32 copies, staples them together, and walks around handing them out to the agents. Our goal is to have the reports print to a file on her PC where she can just attach the reports as an email and send them to the agents.

War Eagle!
Lions Baseball '09!

 

[captaingadget]

Why not, therefore, have the reports output to a folder on the supervisors home file server. You will still have to establish "trusts and permissions" between servers but at least there will be no need for a user to be mapped across domains.

 

[telebub]

Thanks Captain but I met with the Network Security on Friday and explained what we wanted to do and they will not allow it. I don't understand the threat but I didn't argue with them. I gave my apologies to the supervisor and closed the issue. As always, thanks for everyone's assistance.

War Eagle!
Lions Baseball '09!