Question

I got a 9037 error (invalid session) after upgrade from lasserfiche 8.1. How can I fix it?

Laserfiche

Updated May 2, 2014

asked on January 7, 2014

After a upgrade from Laserfiche server and client 8.1 to 9.1, when i try to log in to my repository i got an error 9037.

Answer

SELECTED ANSWER

replied on January 10, 2014

Hi Pablo,

If you can, I'd recommend restarting the Laserfiche service. Sometimes that will fix the issue by itself.

Otherwise, this will require some troubleshooting. In the post above mine, Chris has some great suggestions for beginning the investigation. You can try working it out yourself, or you can contact the support team for more immediate assistance.

Replies

replied on January 9, 2014

Hi Pablo,

Does this happen from all workstations for all users? Can you log in successfully to the Laserfiche client on the server using the Laserfiche Admin account?

During the upgrade have you migrated the server or was the migration on the same server? Has anything else changed in the environment as part of the upgrade?

Hopefully this might point us in the right direction to start off with :)

Kind Regards

Chris Douglas

replied on January 12, 2014

Thak you for the help. The problem was that during the install the program generate a new file for the license and put that file in the server desktop. I just transfer that file to the sever folder, restart de lf service as you suggested and everything works fine.

Thanks a lot.

replied on May 1, 2014

Does anyone know what is causing this? It appears to be happening in 9.1.1 as well and sure enough restarting the Laserfiche Server service allows you to login again. It only appears to effect Named Users and the ADMIN account and not Retrieval users.

replied on May 2, 2014 • Show version history

I have a client we just updated from 7.2.1 to 9.1.1 that is getting this error randomly from various clients as well - has there been any movement on this? They are on TEAM licensing, so no named users, just concurrent.

replied on May 2, 2014

Please open a case with Laserfiche Support so this issue can be looked into further.

You are not allowed to follow up in this post.