Question

Can't create a repository

Version 9 Administration Laserfiche

Updated January 15, 2014

asked on January 13, 2014 • Show version history

When I try to create a new repository I get a message with error code 9025, the repository is misconfigured. When I look in the Event log, I get the message with eventid 10166 "There was an error attempting to execute SQL when creating or attaching a repository: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified; SQL State: IM002; Native error code: 0; Database server: xxxx; Database/Schema: yyyy"

I'm running the most recent version of Laserfiche on a Windows 2008 R2 64-bit system. I'm running SQL Server 2008 R2 64-bit, installed on the same machine.

Is Laserfiche trying to use 64-bit SQL/ODBC or 32-bit? If LaserFiche is trying to run 32-bit and I've got the 64-bit SQL installed, that might be the issue.

Any other advice or suggestions are greatly appreciated.

Thanks in advance.

0 0

Answer

APPROVED ANSWER

replied on January 13, 2014

Are you using named SQL instances or just the default? For example, when you launch SQL Server Management Studio to connect to the SQL Server, are you just entering in something like [servername] or are you entering in [servername]\[instancename]? Whichever it is, please confirm that you are specifying the SQL Server in the same manner when using the Repository Creation Wizard.

If the issue still occurs, then you can try removing the SQL Native Client currently installed on the server and then install the version of SQL Native Client that ships with the Laserfiche Server installation package you have.

If that doesn't help either, then please contact Laserfiche Support for further assistance.

1 0

Replies

replied on January 15, 2014

Please check the repository access rights. Using the Laserfiche Client, log into the repository as an admin user. Then right click the root of the repository and go to "Access Rights". From there, make sure that the user you are wanting to use has the "Create Folders" and "Create Documents" access rights granted. You can refer to the Security section of the Client help file for more information.

Regards

2 0

replied on January 13, 2014

This sounds like the logon account that LFServer is running as, may not have the proper permissions on the DMBS.

0 0

replied on January 13, 2014

No, that's not it; I already checked that. Thanks.

Just to be certain, I changed the userid used for the LaserFiche Server service to my own userid, and I KNOW that one has the right permissions. I got the same results.

????

0 0

replied on January 15, 2014

I reinstalled the LaserFiche client and now it works....

However, now that I've created the repository, I can't create a folder or an entry or import anything. When I right-click from the client and select New, both Folder and Document are grayed out.

Any advice?

Thanks in advance.

0 0

replied on January 15, 2014

Can you confirm that the user has the necessary access rights granted in the repository? Specifically the "Create Documents" and "Create Folders" access rights?

Regards

0 0

replied on January 15, 2014

Yes.

When I use the admin console to right-click the volume they're on, select Security, and select the domain user I'm logged in as, It tells me I have Create Documents and Create folders. I'm also a Trustee.

But when I go through the client and do the same thing, it tells me I do NOT have those access rights.

I'm very confused.....

0 0

replied on January 15, 2014

That got it... thank you.

I imagine I should create some groups and apply these Access Rights to them rather than individuals, then put the individuals in the groups. Is that a good way to go about it?

Thank you for your help.

0 0

replied on January 15, 2014

Using Laserfiche groups would be recommended for this. If you're using Windows accounts then you can even configure security directly on configured windows groups.

0 0

You are not allowed to follow up in this post.

Question

Question

Can't create a repository

Answer

Replies

Sign in to reply to this post.