Unmanaged Disk - setting up the job server defaults

[sugabutt]

Hi, I'm in a mess... need your help please.
Our CMC was setup with many reports being run on a schedule, and the PDF files were automatically saved to a network drive/folder. In each report, the destination was set to "unmanaged disk" and the 'save to job server defaults'. Everything was working fine, until our network server (the destination server) changed names.

I went into the reportjobserver or the destinationjobserver (can't remember which because I went into both of them so many times) and found the UNC path of the old server name and changed it to the new name. But it won't work. Getting a 'Failed' and the message says "source file error. CrystalEnterprise.DiskUnmanaged: Invalid Argument".

Can someone tell me exactly where in the CMC Server section I need to setup the default destination... is it the Destination job server, or report job server, or none of the above?

 

[MJRBIM]

Did you also RESCHEDULE all your old RECURRING instances...?

The old network server name is BOUND to those old RECURRING instances. It does not pick-up the change to the DEFAULT at run-time, only when the Job is CREATED.

What happens if you create a new SCHEDULED instance from Scratch..?

Senior Business Intelligence Consultant
Toronto, Canada

SeagateInfo 7 -> Crystal Enterprise -> BOE-XI (R2) / (R3.1) | Crystal ( 7 -> 2008) design | WebI design | Best practices for Java / .Net / Web Services

 

[sugabutt]

Tried that, and tried it just now again, but that did not work. Got the same error message as before.

 

[MJRBIM]

Does the "network account" that is running your BOE services have permissions to access the specific UNC-Path that you have defined in the UNMANAGED DISK settings...?

Senior Business Intelligence Consultant
Toronto, Canada

SeagateInfo 7 -> Crystal Enterprise -> BOE-XI (R2) / (R3.1) | Crystal ( 7 -> 2008) design | WebI design | Best practices for Java / .Net / Web Services

 

[sugabutt]

What we did to fix our problem was did a search in the Registry for our old server name, and found an entry that was the job server's default destination path. We changed it to the new server name and it worked.

I noticed before we did this that even though I changed the name in the Report Job Server and Destination Job Server, if I stopped and started the server, it would chanage itself back to the old name.

Heather