B4Print.com

Workflows => Artwork Systems => Topic started by: G_Town on January 03, 2008, 06:36:52 AM

Title: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 06:36:52 AM
We have 2 nexus boxes and have updated the versions on both also we nuked all the workflows and created all new ones mainly as a training exercise but also because the workflows were originally created about 37 years ago.

Started on one box doing all the basics, impo, screen page, proofing etc then saved them all and then restored them to the other box. The weird thing is now on the second box all the files are dropping right on to the root level of our server and not onto the nexus box (the first box is working fine). I am poking around in Nexus manager and comparing the workflows but I don't see any difference.

Any ideas?

Thanks
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: marko on January 03, 2008, 07:14:56 AM
My guess is the paths/mount points for the 2 boxes are different.

Go to the copy file mod (or like) and reselect.

Hope it helps
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 10:24:21 AM
What module do I change that in?

I've checked them all and they are all identical to the box thats working fine, is there some global preference I am missing or do I literally need to browse to the correct nexus box and define the path since default doesn't seem to work??
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 03, 2008, 11:02:41 AM
Have you checked all of your server settings in your Nexus Manager preferences? There are some paths in there though I don't remember which ones exactly and I'm not at work right now.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 12:10:28 PM
Quote from: Joe  on January 03, 2008, 11:02:41 AMHave you checked all of your server settings in your Nexus Manager preferences? There are some paths in there though I don't remember which ones exactly and I'm not at work right now.

Lucky you, I'll check that next thanks.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 03, 2008, 12:20:15 PM
Not all that lucky. I'll be at work in a few short hours. >:(
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: marko on January 03, 2008, 01:42:10 PM
Are the mount points on both Rips the same? Example: Is the drive letter storing the files the same letter on each box?

Where are you storing the files (S:\whatever)? Is that the same on each box?

This can be found in the workflow itself in the module that is coping the files over.




Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 03, 2008, 01:56:38 PM
I don't think the oppo files get copied anywhere except the jobs folder unless they are using a copy module to specifically copy the oppo files to another location, do they? And the jobs folder is in the Nexus application folder. Strange they would be showing up on other drives unless they are actually copying them with a copy module.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 02:11:25 PM
Quote from: Joe  on January 03, 2008, 01:56:38 PMI don't think the oppo files get copied anywhere except the jobs folder unless they are using a copy module to specifically copy the oppo files to another location, do they? And the jobs folder is in the Nexus application folder. Strange they would be showing up on other drives unless they are actually copying them with a copy module.

Thats the weird thing the templates all look like the screen shot with everything defaulting to the jobs folder which is exactly the same as the other box that is working fine. The only thing I can think of is there is another setting somewhere that I am missing but I'll be damned if I know where it is.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 03, 2008, 02:13:25 PM
Yeah, that template is just for the naming convention. The location is only defined in the copy module. Are you using any hotfolders or shuttle?

What is the actual drive letter of your Nexus app and the drive letter where these files are showing up?
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 02:25:43 PM
Quote from: marko on January 03, 2008, 01:42:10 PMAre the mount points on both Rips the same? Example: Is the drive letter storing the files the same letter on each box?

Where are you storing the files (S:\whatever)? Is that the same on each box?

This can be found in the workflow itself in the module that is coping the files over.






The E drive is the Nexus Box and the L drive is our server and it is dumping the ps/oppo files into a folder on the root directory of our L drive and in none of the modules does it use a backslash to specify creating a folder.

There only copy modules for copying the screen pages to one folder and for copying the eps link file to another folder and we specify these by job.

Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 03, 2008, 02:38:53 PM
Well I re made a WF on this box from hell and its doing the exact same thing so that rules out the workflow ,doesnt it?

The weird thing is everything works I get what I need I just have this temp crap ploping onto my server rather than the jobs folder on the Nexus box. Perhaps there is something wacky with the install.

Maybe its time, GULP, to call support.
 :-\
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 03, 2008, 05:18:22 PM
Check out the colored lines between the modules from one Nexus Server (good one) to the other one (bad one). They need to be exactly the same (as the good one).
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 04, 2008, 08:12:26 AM
Quote from: Joe  on January 03, 2008, 05:18:22 PMCheck out the colored lines between the modules from one Nexus Server (good one) to the other one (bad one). They need to be exactly the same (as the good one).

Yea checked that, the dependencies are exactly the same (which they should be since the WF was restored from the good box). Every WF is doing it as well dunno if I mentioned that yet which makes me think its something about the setup of the box.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 04, 2008, 10:03:58 AM
Have you tried doing an uninstall and re-install? Also check in Windows Control Panel | Add/Remove programs and make sure there isn't more than one install of Nexus (I'm thinking you might be running it on a Mac though).
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 04, 2008, 11:16:44 AM
Quote from: Joe  on January 04, 2008, 10:03:58 AMHave you tried doing an uninstall and re-install? Also check in Windows Control Panel | Add/Remove programs and make sure there isn't more than one install of Nexus (I'm thinking you might be running it on a Mac though).

Nope it's on a winders box, um I do have another install of nexus on this same box its set up just like the other one.

Long said the same thing (uninstall reinstall) is there an issue of having 2 installs on the same box?

When I started here they had like 3 on each (older versions) so I assumed it was ok?

Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: Joe on January 04, 2008, 11:22:26 AM
You can have more than one install as long as they aren't the same version. ie...you can have 8.3, 8.4, 8.5 on the same machine but not two of 8.3 or 8.4 or 8.5. And don't try to run two at the same time or hijinks are sure to follow.
Title: Re: Temp/oppo files landing on server and not Nexus Server
Post by: G_Town on January 04, 2008, 11:28:54 AM
Oh ok I'm safe then, all I can think of is I somehow pooched the install. Gonna wait for the second shift guy to come in to show him (hopefully the right way) how to do an install.

Thanks for you help.