XML error

[BarbaraSalfate]

Hi, We have a problem since yesterday. All the user with spin-o-matic can´t work with the application (not the cluoud app). I want to know if there some disconection or desability from this app. But the cloud app is working fine. We don´t understand this diference. Best regards and Thanks in advance. Bárbara

[mgobat]

Please upgrade to the latest version manually. You may download it from https://github.com/ExLibrisGroup/SpineOMatic/releases/download/v8.1.2/SpineLabeler.exe

[UAlbanyErich]

We are seeing the same issue. It was reported to from a user with v7.0, but I'm getting the exact same message for v8.1.2.

The URL in the AlmaAccess tab with the API attached (https://api-na.hosted.exlibrisgroup.com/almaws/v1/items?item_barcode={barcode}&apikey={APIkey}) works in a browser though, so it's not the service or the APIkey.

[BarbaraSalfate]

Hi, we are update it to v8.1.2 and for some user worked and other not and we know isn´t the API because is working fine. We are trying to see what is wrong but we don´t know yet.

[UAlbanyErich]

Considering that the SpineLabeler hasn't changed in the last two weeks, the change must be on the ExLibris end. Maybe the "fix" needs to be in SpineLabeler or maybe at ExLibris, but in the meantime, we're struggling with much more manual and inefficient label printing.

Any confirmation and/or comment by the repo owners?

[mgobat]

@UAlbanyErich, so after upgrading to 8.1.2, you still have this issue for all users? We released version 8.0.0 to address an issue with still using TLS 1.0 in version 7.0, and that update was carried through to all subsequent releases. I'm checking with the cloud team to see if anything changed there last week; but its odd that upgrading to 8.1.2 for other customers solved the problem. I'll update the issue if I learn anything from the cloud team. Thanks for your patience.

[mgobat]

@UAlbanyErich, could you please create a Support incident and report back the case number so I can push it through? Thanks.

[Deboracapon]

Hi, We have the same issue. It was reported from a user with v7.0, I upgrade to 8.1.2 and 8.0.0, and still the same, for now, we are using the cloud app, but is not working well with our classification labels.

[UAlbanyErich]

Sorry for the delay. I'm not used to submitting ExLibris support tickets. Case 06418671 is now created.

[mgobat]

@Deboracapon, generally, this error occurs if the workstation is using a version of TLS < 1.2. The application defers to the operating system to set the TLS version. Alma doesn't like anything less than 1.2. Can you request your IT folks check? Thanks.

[UAlbanyErich]

@mgobat It would be pretty unusual for a Win10 system to not be using TLS v1.2 these days. According to this, it is certainly the default for every cypher suite. An organization would have to actively work to disable it (manually or via GPO). That is definitely not the case for us, and we are getting the same error.

[mgobat]

@UAlbanyErich, could you please provide a few barcodes which should work? You can email me privately, if you prefer: mark.gobat@clarivate.com

Thanks.

[UAlbanyErich]

Ha! As with many technical problems that mysteriously don't work, we tried one last time with a new setup of v8.1.2 (exact same settings - from a settings file, not manually entered), and it worked!

I truly wish I could understand why it repeatedly didn't work and then did, but there are plenty of other priorities now that we need to deal with.

Thanks.

[mgobat]

@UAlbanyErich, agreed about technology issues. For example, my wired internet at home is working just fine right now....but my wireless internet went away....and of course, the source for both is the same router. But the wireless network is working fine internally. Huh.

Glad you are up and running!

[Deboracapon]

@UAlbanyErich @mgobat mysteriously happened the same to us yesterday, our IT was looking with me at the TLS thing... we are in 1.3 and then I tried once again to set up v8.1.2, and worked!! jajaja.

Technological mysteries... Thanks for all, and have a good weekend

[mgobat]

@BarbaraSalfate, is it working for you folks now, too? Thanks.

[BarbaraSalfate]

Hi, yes is working for us now. I had a essue with it but I delete and install it again and now is working fine.