Hi Guys,
So initially I posted about my client having issues using the server with errors caused by the Database which we resolved by reverting the server to an older state (he didn't mind the lose of data).
However, given that this software is the centre of his business, to be able to give him better support and minimise downtime. I decided to install a brand new instance for him.
New HDD (old ones remain as is) running Centos 8 with VirtualBox installed.
Installing Windows 2008 R2 using the WIM left by the vendor who did the setup for him initially. Going through the steps outlined in this forum (https://www.printroot.com/forum/f17/installation-prinergy-2220/) which it all went straight forward.
Until we needed to communicate with the achieve Platesetter, for the life of me I can't this thing to communicate to the server and I have tried ALOT of different things.
Setup -
Centos 8 - installed Natively
Virtual Box - Running WinServer 08R2 Kodak version
NIC - two NICs installed both pass through (bridge mode) Second NIC is the GMCE Master Connection with all the items disabled except for IPV4 (IP Config: 192.168.100.209/255.255.255.128) everything else left blank.
When starting the Prinergy Server it all works find and launching print console shows no activity to the platesetter.
Host config I'm unable to run as I dont have a service dongle (could this be?) I get a message when I reboot saying it doesn't have a config as it's newly installed...
The NIC has been setup with checksum disabled for IPV4 and UDP - Jumbo packet has been set to 9014 at both Guest OS and Host OS.
I've setup DHCP server to try and have the platesetter get an IP and it does... if I set reservation to .193 I get no pings back - every other IP does which is weird (I know I dont need DHCP server but I'm now desperate)
On top of all this I can barley FIND any guides/materials of sorts to help out... and thus im coming to you guys for help. Kodak refuse to work with him as he's out of support and calling a few 3rd party support don't seem to be interested given that he's a few major versions behind (btw his licence allows him to update to Ver. 6)
Please guys any help anyone can shed on this I'd really appreciate it. I can work with anyone offline and do a full post on what resolved the issue and hopefully help someone else like me out there.
Thanks in advanced.
Are you just talking about a network connection to the platesetter PC? What kind of data are you trying to send to that PC? Tiff files or some other data. Can you network to other computers on that network? Can the platesetter PC see the CENTOS PC on the network? I have limited experience with CENTOS but I always had networking issues because of the the Firewall on CENTOS.
Platesetter and Server are plugged in directly to each other. Server has 3 NICs:
1- Network (10.1.1.0/24)
2- GMCE Master Connection directly into the platesetter
3- Disabled in Centos
Centos Firewall is turned off and Guest Server 08R2.
When I launch Printer Console, the platesetter is never detected.
Does the platesetter have a static IP or does it look for DHCP?
At one stage I was able to get it to show an IP when I installed a DHCP role on the server but even then Print Console couldn't pick up the platesetter...
Our platesetter just has one bit tiffs going to our platesetter PC. Prinergy just copies them to the tiff catcher software hot folder. All of our computers have static IP's.
Does your platesetter PC have an ARAXI account on it with the same ARAXI password as the Prinergy server. If not it needs to have it.
Yes it does, was setup during the installation process.
I can start the server no issues with all the modules and applications but it can't see the platesetter at all... Looking at the firmware folder the. ini file shows what up the pc has to be 192.168.100.209 255.255.255.128... Is any of this sound right to you?
Does the platesetter need a dhcp assigned iP?
What is the IP address of the VM operating system that Prinergy is running in?
192.168.100.209 255.255.255.128 - gmce
10.1.1.15 255.255.255.254 - primary NIC
You may be fighting a losing battle.
As far as I can tell Prinergy does not support running in a VirtualBox VM. Their documentation states it must be running on VMware vSphere (https://www.vmware.com/products/vsphere.html). We looked into it once and decided the requirements, and there are many, were more complicated than running it in a stand alone server. Also the feature to run in a VM may not have been an option back in Prinergy 5.3.
Have they ran Prinergy previously in a VM? A VirtualBox VM? If not, why try it in a VM now and why a linux OS like CENTOS?
All good questions and to give you some context here is a short version of the story:
Owner of the printing company has had his install for over 10+ years and suddenly database has issues starting and the whole thing comes down.
The client has made the mistake of NOT renewing his support with Kodak and thus when asked for help/support it was refused.
Then I came into the picture as their adhoc Tech guy.
Centos: it's very stable platform and known to be compatible with most Dell Server hardware
VirtualBox: Best free option on the market right now and the ability to passthrough a lot of devices directly into the guest. i.e USB dongle
I should have outlined as well, their previous Native installed Windows 2008 R2 is having the exact same issue! and thus right now I'm stuck for options on what to look at.
Hopefully this gives you a clearer picture.
But was their Prinergy server ever running in a VM? I cannot find any Prinergy documentation that says it will work inside a Virtual Box VM nor can I find any information fro running Prinergy 5.3 inside of any VM.
Attached are two documents related to running Prinergy in a VM.
Thank you for providing those documents. Though they do shed some light and some further things to try out.
Would you happen to have anything relating to the GMCE Master Connection and best way to have the platesetter plugged into the network (either it be directly attached to the server or via a network switch)?
Or a document outlining new installs from start to finish - that would be helpful too
Keep in mind I'm still learning about this system and quickly finding out how finicky it is!
Worst case scenario I re-install Windows Server 2008 R2 back natively and go from there
It sounds like Prinergy drives your platesetter directly and I have no experience with that. Our platesetter has a stand alone PC with tiff catcher software so Prinergy just sends one-bitt tiffs to that PC via our local network to a hot folder to the platesetter software. You could try just going through a switch from Prinergy to the platesetter.
One thing you posted is:
Quote192.168.100.209 255.255.255.128 - gmce
10.1.1.15 255.255.255.254 - primary NIC
Is the one labeled gmce the 2nd network card on the CENTOS Server or the network card on the platesetter and primary NIC is in the CENTOS Server?
VirtualBox uses virtual a NIC. What is the IP address it gets assigned. This would be your Windows OS and Prinergy's IP address. Since the Primary NIC has an IP address of 10.1.1.15 does the VM network use that sam2 IP range, 10.1.1.x, as the Primary NIC? If so that could be the problem as the Prinergy server would be on a different subnet than the gmce card. That is assuming all of my above assumptions are accurate.
I'm not sure what the recommended setup is... this is how it was setup previously.
If you are saying I can use router/switch then I can try that as well.
As for the network cards, they are both on the server:
gmce - that plugs directly into the platesetter - No config on Centos and on VirtualBox it's passing it through as a NIC
Primary is plugged into an ISP network for Internet on Centos and also on Guest OS (both passing through, thus they get dhcp LAN addresses from the ISP router)
Therefore the platesetter and Server are on the same subnet.
What I don't understand is:
QuoteAs for the network cards, they are both on the server:
gmce - that plugs directly into the platesetter
so you have the gmce card in the CENTOS server and it plugs directly into the platesetter? Plugs into where and what on the platesetter? Via an ethernet cable to a NIC that is installed into the platesetter? Or what? Or is it something like a SCSI, Firewire, or USB connection?
I think I may have confused you when I said GMCE... There is a Ethernet Cable that comes out of the Platesetter and plugs directly into the Network Card of the server as described earlier.
In one of the guides I found it said to name that LAN connection to GMCE Master Connection hence why I called it that earlier.
Hopefully this clarifies it. haha
OK so there is no PC at the platesetter? The ethernet cable plugs into the actual platesetter and not a NIC in a PC?
Ok here goes;
Server NIC 1 <> Router (Ethernet)
Server NIC 2 <> PlateSetter (Ethernet)
PC/Server has Centos installed which within I've installed Windows running VirtualBox
Quote from: menzy on April 22, 2020, 08:47:30 PM
Ok here goes;
Server NIC 1 <> Router (Ethernet)
Server NIC 2 <> PlateSetter (Ethernet)
PC/Server has Centos installed which within I've installed Windows running VirtualBox
And yet I still do not know what Server NIC 2 <> PlateSetter (Ethernet) cable is being plugged into. One end of the cable goes to Server NIC 2 and the other end goes to the PlateSetter. I'll assume it is in NIC in the platesetter. Are you sure the cable going from Server NIC 2 <> PlateSetter is good? If so are you sure it is wired correctly between the two devices? ie...a straight or crossover cable.
QuoteWhen you connect two devices of different types together, you use a straight through cable. When you connect two devices of the same type together, you use a crossover cable. If you insert a network device between two devices of the same type, all cables are straight through.
Yes Ethernet on both ends
This cable worked previously and I've checked and can confirm its a crossover eth cable.
See what you did there? You've skillfully avoided answering the same question again. I know it is ethernet on both ends. It must be some kind of state secret that you are unwilling to answer but I'm game to try one more time...what is the ethernet cable at the platesetter plugged into? Is it a standard off the shelf common network adapter card or is it some kind of proprietary communications board? I'm guessing the latter but who knows?
OK if you are sure it it is the right known good cable then it must be a problem with the communication parameters on the Prinergy server. You stated that "Second NIC is the GMCE Master Connection with all the items disabled except for IPV4 (IP Config: 192.168.100.209/255.255.255.128) everything else left blank" so I assume that is the way it was setup when the system was working previously. I have no idea what those settings would be or where they are located. They could be in the Prinergy database but I doubt that. I think the most likely location for these settings would be in the Prinergy settings within the Windows registry database. If you still have the old working Windows install of when this was working you could try searching through it and see if you can find any settings that look they would be the ones that communicate with the platesetter. Other than that I am out of suggestions.
QuoteThe client has made the mistake of NOT renewing his support with Kodak and thus when asked for help/support it was refused.
Just to clear this up....Kodak will not refuse support because a person doesn't renew his support. They do refuse to give free support to anyone though.
Ok - we have made a lot of progress over the last couple of weeks.
I'm now to the point where the server starts with no problems and it even detects the Platesetter...
However, when I launch "Print Console" ver 4.44 - it says initialising and the messasge shows "the device is attempting to connect to the licence server. Please wait."
However this will eventually time out and say that it couldn't contact the licence server. I'm so close! any ideas?
You need to go into the licensing area and make sure it is pointing at the Prinergy Primary. I have no idea where that is at in the Print Console but it looks like this in Preps. The circled area should either be the Prinergy Primary PC name or IP address. Since you see it saying it "is attempting to connect to the licence server. Please wait." there has to be someplace to enter the info for the licensing server (Prinergy Primary)
In the time I put in my last response.. I now can't even start the server anymore...
getting this error:
E 23May20 15:05:26.765-GMT+11 [4440.1992] BLW2K8 ARAXI PChangeJobShare DBIF_DBConnection.cpp(102): Hung connection detected, exiting process
Any ideas?
Also thank you so much for your help so far!!!
Hi Joe,
Any ideas on my last reply please?
Thank you
There is another thread
here (https://www.b4print.com/index.php?topic=9798.0) that also a user was having errors with PChangeJobShare. He got it fixed by re-installing but he found some things along that way they may or may not help:
Quote from: joaodaffonsojr on October 16, 2019, 08:01:37 AMNot sure what specifically was the cause of the error, but with these tips the instalation was successfully!
– The Machine cannot be named PRINERGY or PRIMARY, in my case was named PRINERGY
– Windows firewall must be OFF
– the password cannot have special characters , my case had "@"
– The IP address must be fixed one not provide by DCHP
– Let the installer create the ARAXI user during the instalation, I created the user before.
Also I checked on the Kodak Partner Place about password issues and found this:
Password is all setup with no issues and was during the setup of Prinergy Server (ARAXI user was created by the wizard and password was set as ARAXI as well) This was working fine a week ago.
Anything else to try before we go down the route of re-installing again...
There is a file named PChangeJobShare.exe here on my system. You may investigate its use.
QuoteDatabase Cleanup 8.2.0
Database Cleanup (Build 0 - Sat Mar 31 15:08:28 2018) Araxi v8.2.
⌐ 2018 by the Eastman Kodak Company. All rights reserved.
Usage: PChangeJobShare.exe targetFileServer targetFileShare -h <s
> -s <sourceFileShare> [-a]
PChangeJobShare.exe targetFileServer targetFileShare -j <j
PChangeJobShare.exe -r
PChangeJobShare.exe -l [ -pathCount [ <shareName> ] ]
PChangeJobShare.exe fileServer fileShare -x
PChangeJobShare.exe fileServer fileShare -w
PChangeJobShare.exe -y
-h the host to move database file location records from
-s the share to move database file location records from.
-r recovery mode. Continues a previously interrupted instance.
-a show all the conflicting files if any when changing job share
-l show the list of file server names and share names in the dat
-x change regFilePathName into Helios storage format for the giv
hare.
-w change regFilePathName into Windows storage format for the gi
share.
-r recovery mode. Continues a previously interrupted instance.