Hopefully someone is around to help me out...'Cuz I am stuck.

We had to move my workstation to get ready for a remodel.  I've got everything hooked back up and everything is working independently.  However, I can't get prinergy to send my proofs to the printer.  Normalizing, Color Matching, Trapping, and Optimizing all work great.  It's when it gets to the File Moving Stage it get caught up.  It's giving me a "failed to create temporary folder" error. 

I can use my EFI Client to print.  But Prinergy won't send the files...

Anybody got some troubleshooting ideas?

Do you have am  Araxi user (password "ARAXI") created on the computer you are trying to send to? You have to if you want to send files to it.

If that isn't it...

We get this sometimes sending files to our CTP. Try restarting the computer that Prinergy is sending the files to. This usually works for us but not always.

Gotcha, so I'm guessing(hoping) that the Araxi is the issue. 

It is the same exact server I have been using all along.  Is this something that could have been reset during the move? If so, how do I check for and/or create an Araxi User?

What is the OS? I'm guessing Windows 7? If so...Start, Settings, Control Panel, Users. (I think).

Moving a computer shouldn't have deleted an account though so this probably isn't the case. Can you see your EFI PC from your Prinergy Primary on the network?

Yeah I've still got the original account.  I can see the EFI PC from the computer I run Prinergy on.  I will go check the actual server now.  And yes it is a Windows 7 that is running EFI.

Quote from: zacgil on February 10, 2015, 07:15:38 PMYeah I've still got the original account.  I can see the EFI PC from the computer I run Prinergy on.  I will go check the actual server now.  And yes it is a Windows 7 that is running EFI.

OK. If it is anything like our CTP Windows 7 PC's...reboot the EFI Windows 7 PC and try it again. That almost always fixes it for us when we are getting that error. You can also check the folder permissions on the EFI PC. It should be set to "Full Control"for "Everyone". (Right click the folder, Sharing, Permissions or something close to that.)

So I found the Proofers in Network Connections, but I do not have access.  I'm guessing this is why there is an issue.  And now I'm trying to figure out how to give access to my Prinergy Server....

Quote from: Joe on February 10, 2015, 07:24:11 PM

Quote from: zacgil on February 10, 2015, 07:15:38 PMYeah I've still got the original account.  I can see the EFI PC from the computer I run Prinergy on.  I will go check the actual server now.  And yes it is a Windows 7 that is running EFI.

OK. If it is anything like our CTP Windows 7 PC's...reboot the EFI Windows 7 PC and try it again. That almost always fixes it for us when we are getting that error. You can also check the folder permissions on the EFI PC. It should be set to "Full Control"for "Everyone". (Right click the folder, Sharing, Permissions or something close to that.)

Everything seems to be set to Full Access and Everyone.  It just won't let me click into the Prinergy server from EFI computer, as I don't have permission.  I will try to restart and see if that helps.

Your probably not connecting directly to printers are you? My guess is you are sending files to a hot folder on the EFI PC right. If so check your permissions on the shared folder on the EFI PC. This one:

[attachimg=1 width=400]

See my previous post.

Quote from: zacgil on February 10, 2015, 07:30:05 PM

Quote from: Joe on February 10, 2015, 07:24:11 PM

Quote from: zacgil on February 10, 2015, 07:15:38 PMYeah I've still got the original account.  I can see the EFI PC from the computer I run Prinergy on.  I will go check the actual server now.  And yes it is a Windows 7 that is running EFI.

OK. If it is anything like our CTP Windows 7 PC's...reboot the EFI Windows 7 PC and try it again. That almost always fixes it for us when we are getting that error. You can also check the folder permissions on the EFI PC. It should be set to "Full Control"for "Everyone". (Right click the folder, Sharing, Permissions or something close to that.)

Everything seems to be set to Full Access and Everyone.  It just won't let me click into the Prinergy server from EFI computer, as I don't have permission.  I will try to restart and see if that helps.

If restarting the EFI PC does not help go to your Prinergy Primary server, not from your Mac or wherever you are using Workshop from, and try to access the EFI share and try to copy a file manually from the Prinergy Primary to the EFI hotfolder shown above. If you can't copy a file manually then you have networking issues between the two.

I still wasn't able to get into the EFI folder from the Server.  Still no permission/access.  I got the night shift coming on now so I'm going to have to use my work arounds and get back at it in the morning.

I do appreciate the help.  It's definitely given me some options.

This may be out of left field but are there any strange characters in the PDF's name? I've had prinergy run everything through then fail after making a preps job for no reason.

I know it's not the same but prinergy's error codes are cryptic. Also, have you rebooted prinergy? Sometimes that clears up issues.

You said you moved your workstation but did the EFI and the Prinergy server get moved to another network port as well? If so, is it possible one of those network ports are on a subnet?

Quote from: Farabomb on February 11, 2015, 08:18:14 AMThis may be out of left field but are there any strange characters in the PDF's name? I've had prinergy run everything through then fail after making a preps job for no reason.

I know it's not the same but prinergy's error codes are cryptic. Also, have you rebooted prinergy? Sometimes that clears up issues.

The names are the same as I've used before.  But I have seen that be an issue.  All the ports are the same, we have just needed to extend some ethernet cables. 

I have not tried to restart Prinergy yet, and I should have tried that last night.  I'm going to shut off my mac and the EFI comp, restart the Server and then boot back up the EFI and Mac.  I've heard that the order in which you turn off/on can cause issues as well.