Question

Access Denied [9013] error after Laserfiche 12 upgrade of web client

Web Client Version 12 Installation and Upgrades

Updated October 16

asked on October 15

I upgraded one of my production environments from 11 to 12 last night. Now when using Web Client go to a repository, we get this error:

We weren't getting is error with LF 11.

9 times out of 10, if the user refreshes their browser, it will log them into the repository. If they click the hyperlink to sign out of directory server, it will log them into the default repository as set in web client.

0 0

Answer

SELECTED ANSWER

replied on October 16

After working with my Solution Provider, it appears that the solution for this is to unselect the Only sign in with SSO for the Directory Server on the Services Tab in Web Client Configuration and Save the change. Then re-check the option to Only sign in with SSO and save again.

Very random and I hope that it ends up being the final solution.

After this procedure, user's saved bookmarks to our old Web Client server also work once again with the DNS redirection.

2 0

Replies

replied on October 15 • Show version history

I had this too. Didn't happen with the Fall 2024 release of LF12, but did happen with the Spring 2025 release.

Check services on your server. See what user it is using for the Laserfiche Repository Server service.

In my case, it had been a service user on our domain before the upgrade, but was showing Local User afterwards (or Local Admin or Local Machine or something like that). That local machine user doesn't have permissions to the SQL database, so it resulted in this error. Changing the service's user and restarting the service resolved the issue.

Had to have our VAR help me resolve that one.

1 0

replied on October 15

I had to change to my domain based service account after my upgrade as my db server is on a different machine and so the repository service wouldn't even be able to connect to the database as local user

0 0

replied on October 15 • Show version history

I'm about 90% sure that I know what is going on and why we're getting the Access Denied 9013 error. We recently migrated all of our servers to new Windows VMs with different names. As a part of this migration CNAME DNS redirections were setup which seemed to work with LF 11, so users didn't need to change their bookmarks. Now I'm upgrading to LF 12 and seeing a problem with the old bookmarks that go to the old server names.

If we use Web Client URLs with the new server name, the Web Client signs in without error. I'm wondering if Web Client 12 is a little more secure and not allowing the redirection?

1 0

replied on October 15

If you use InPrivate or Incognito mode does it work?

0 0

View 2 previous replies

replied on October 15

No, I get the same. I get a prompt to sign in from the browser but after entering my credentials, I get the same error.

0 0

replied on October 15

Did you upgrade the Laserfiche Server at the same time?

0 0

replied on October 15

Yes, repository server & web client were both upgraded to Spring release last night

0 0

replied on October 15

Go to the Laserfiche Admin Console, select the Server node and verify that it shows the correct licensing information. If not, relicense the Laserfiche Server and restart the server services.

0 0

replied on October 15

everything looked correct but I relicensed and restarted the service but it didn't fix anything.

0 0

replied on October 16

Despite my optimism that it was caused by using an old URL that redirected. It doesn't seem that is the 'fix'. I have a ticket in with my Solution Provider to have a look and see if they can identify what is going on.

0 0

SELECTED ANSWER

replied on October 16

Very random and I hope that it ends up being the final solution.

After this procedure, user's saved bookmarks to our old Web Client server also work once again with the DNS redirection.

2 0

You are not allowed to follow up in this post.

Question

Question

Access Denied [9013] error after Laserfiche 12 upgrade of web client

Answer

Replies

Sign in to reply to this post.