1402 Error - Client - Intermittent S’abonner

0
Avatar
Legacy Poster

Hello

Only one client receives a 1402 error on an intermittent basis.(3-5 times a week)
This has occurred for several years.
Some other clients have received the 1402, but very rarely.

Able to ping to and from client.
Windows firewall is off.
Overtime, have replaced PC, reloaded bartender software, changed AV software.

This PC along with others are pinged regularly with no issue.
-- Use pinger tool for this

Client is located in a production environent with no external internet access.
Other application run successfully with no issue.

Looked at Seagull License Server and found no issue.
Server and license is rebooted on a periodic basis.


Any comments or suggestions would be helpful.

THanks
FRED

5 commentaires

0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

[quote name='Jones' timestamp='1358521640' post='4118']
Hello

Only one client receives a 1402 error on an intermittent basis.(3-5 times a week)
This has occurred for several years.
Some other clients have received the 1402, but very rarely.

Able to ping to and from client.
Windows firewall is off.
Overtime, have replaced PC, reloaded bartender software, changed AV software.

This PC along with others are pinged regularly with no issue.
-- Use pinger tool for this

Client is located in a production environent with no external internet access.
Other application run successfully with no issue.

Looked at Seagull License Server and found no issue.
Server and license is rebooted on a periodic basis.


Any comments or suggestions would be helpful.

THanks
FRED
[/quote]

Hello Jones,

1. Could you let me know on what Windows OS are you working with BarTender (both on your server and on the client machines)?

2. What version, edition and build of BarTender are you having this issue with?

Thanks!
0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

[quote name='Fernando R-Seagull Support' timestamp='1358523495' post='4119']
Hello Jones,

1. Could you let me know on what Windows OS are you working with BarTender (both on your server and on the client machines)?

2. What version, edition and build of BarTender are you having this issue with?

Thanks!
[/quote]

Thanks
for the Reply

1. Could you let me know on what Windows OS are you working with BarTender
-- XP for both client and server.
-- We have PC acting as a server. We plan to virtualize this soon and put on a server
-- No issues with TCP/IP security limit for XP

2.What version, edition and build of BarTender are you having this issue with
-- Bartender Label, Enterprise 7.72, max 40 printers (we only use 15)
-- Segull license Server 7.72 build 1548
-- WE have not upgraded this since installed with a WONDERWARE APPLICATION.
This was put in by consultants before I arrived.
I think this was installed in 2006.

FRED
0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

Could you try updating both the Seagull License Server (SLS) and your BarTender clients to the latest release available for your BarTender version (v7.75 build 2003)?

You can download both the SLS (SLS775_2003_SR2.exe) and BarTender (BT775_2003_SR2.exe) from our FTP following the below link:
ftp://seagullscientific.com/BarTender/7.75/

Do you still get this error after updating them?
0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

[quote name='Fernando R-Seagull Support' timestamp='1358787915' post='4133']
Could you try updating both the Seagull License Server (SLS) and your BarTender clients to the latest release available for your BarTender version (v7.75 build 2003)?

You can download both the SLS (SLS775_2003_SR2.exe) and BarTender (BT775_2003_SR2.exe) from our FTP following the below link:
ftp://seagullscientific.com/BarTender/7.75/

Do you still get this error after updating them?
[/quote]



**************************************

Thanks for the Reply.

We are also using the Commander.
--- Enterprise 7.72, Enterprise, Build 1548
DO we need to update that too?

What issues are there with upgrading?

We will upgrade as part of the Virtualization process.
Then test and roll back if any issues.
-- Any comments?


This whole process will probably be done in a few weeks or more
since clients are using the system 7 days a week.
But I will update.



Thanks

FRED
0
Avatar
Fernando Ramos Miracle
Modérateur
Actions pour les commentaires Permalien

Indeed you should always be working with the latest release available so please do update all your BarTender clients (including those using Commander).

Remember that you should deactivate your license before performing the virtualization and reactivate it back when it's done (the license can be deactivated/activated through the Seagull License Server, no need to do this over BarTender). Otherwise the Seagull License Server will detect hardware changes and might stop working.

Also remember than when working on a virtualized environment you need to set a static MAC address for the virtual network card and a static CPU ID for the virtual processor. Also make sure to maintain Memory and Hard drive the same (although these are less likely to change unless doing it on purpose). This way you'll avoid issues related to hardware changes.

Finally please note that this license is quite old and it's not compatible with Windows 7, Windows Server 2008 (both R2 and Standard), Windows 8 and Windows Server 2012.

Vous devez vous connecter pour laisser un commentaire.