Possible Bug Issue with OnNewOutPutFile Callback Rule

[Kharvey]

Was this bug ever fixed? I am currently having the same problem when I try to use a server path when I output the file. I am able to output the file to my c:\ drive but not any server.

[Dan Korn]

Originally Posted by Kharvey

Was this bug ever fixed?

Yes, the crash to which the earlier posts were referring, referenced as case FP-11043, was fixed a while ago, back in FusionPro 7.1.

Originally Posted by Kharvey

I am currently having the same problem when I try to use a server path when I output the file.

No, you're not having the same problem. As I mentioned in my previous post, the crash the original poster was seeing actually didn't have anything to do with the OnNewOutputFile Callback Rule. And it was only an issue in FP Server, not FP Desktop. Plus, the symptom wasn't just that the files couldn't be written, it was a program crash. So, while you are definitely having a problem (although you haven't really specified exactly what it is), I'm certain that you're not having the same problem as in the original post.

Originally Posted by Kharvey

I am able to output the file to my c:\ drive but not any server.

What exactly are you not able to do on the server? Do the output files not get created at all? Are there any relevant messages in the composition log (.msg) file?

Without seeing your job or knowing more about your network architecture, or exactly what kind of failure mode you're seeing, let alone what version of FusionPro and operating system you're using, I can't do anything but guess as to the cause of your issue. That said, the most likely causes of your issue are:

1. You haven't properly specified the network path in your rule. In JavaScript, backslashes have to be escaped with double backslashes, so a UNC path which starts with two backslashes has to be escaped with four backslashes. For example:

   FusionPro.Composition.outputFileFullPathName = "\\\\server\\share\folder\\" + Field("foo") + ".pdf";

2. The network path specified is incorrect.
3. You don't have write access to the network share from the account under which the composition is running. If you're using FusionPro VDP Producer via DL Queue or some other server-based application, then you need to make sure the account under which the composition is running has write access.

In any case, the .msg file should offer some clue as to what's going wrong.

[Kharvey]

Thanks for your response. I have verified my path was correct this issue has been resolved it was an issue with the account having access to the unc path that I was trying to compose to.

This issue has been resolved.