Question

SQL Native client 2005 not installed: continued

Version 9 Installation and Upgrades

Updated March 14, 2016

asked on October 21, 2014

My company is upgrading to 9.2 and we are spreading out Laserfiche software across our infrastructure at the same time. (i.e. Laserfiche SQL on one server and Laserfiche Server on another.)

Laserfiche SQL specs: MSSQL 2012, Windows Server 2012 R2

Laserfiche Server specs: WIndows Server 2012 R2, Windows Message Queuing

I am having trouble registering the repository on our new Laserfiche Server, it keeps giving me the: "SQL Native Client 2005 not installed error."

I have followed other threads regarding this issue:

1. Make sure only 1 Native SQL driver is installed and use what is installed with the software

We re-installed Laserfiche Server 9.2 and made sure only one native driver was available. See attached photo.

2. One caveat was that the original database that was being used for the repository registration may have been restored to the new SQL Server improperly.

We did not detach the database. We actually restored from a SQL backup and re-sync SQL users. Is this an issue? We did not get any errors when we restored the database.

Capture.JPG (51.77 KB)

| Download

0 0

Replies

replied on October 22, 2014

Could you please uninstall the SQL Native clients currently installed on the machine and then install the SQL server native client 2005 that ships with LF install package?

0 0

replied on October 22, 2014

Laserfiche server 9.2 comes packaged with SQL 2008 native client...

In this case, should we still uninstall SQL 2008 native client and reinstall the 2005 version?

0 0

View 3 previous replies

replied on October 22, 2014

Can you confirm that you are using Laserfiche Administration Console 9.2.0? When you are using Laserfiche Server 9.2.0 and Laserfiche Administration Console 9.2.0, then it should be using the SQL Server 2008 R2 Native Client during repository creation/registration from the wizard.

0 0

replied on October 22, 2014

Yeap everything is matching. We installed this server from scratch a few days ago. See attached file as proof.

Capture2.JPG (12.48 KB)

| Download

0 0

replied on October 22, 2014 • Show version history

Is the full message you're seeing, "Please ensure that SQL Native Client 2005 is installed and that the database credentials are correct."

Can you confirm that the credentials being used to connect to SQL are valid? You've mentioned that the Laserfiche Server is on one computer while SQL is on another. When you are registering the repository and at the screen in the wizard where you specify the connection to SQL, are you using SQL credentials or Windows Authentication? If you are using Windows Authentication, then it will use the Laserfiche Server service account to try and connect to SQL. In that scenario, you'll need to ensure that the Laserfiche Server service account is a domain account with rights to SQL. If it is just using the Local System account or another account without rights to SQL, then you'll see the error message you initially mentioned.

If you review the application event log on the Laserfiche Server computer, you may get more details about the issue.

0 0

replied on October 22, 2014

Yes that is the error we are getting.

I tried using SQL Server Authentication instead with "sa" and I still see the same error.

When I look at the event viewer. All LFS says is "Register repository failed. Invalid DBMS type."

0 0

replied on October 22, 2014

This may be something that requires the assistance of your Laserfiche reseller. I'll have someone get in touch with you.

0 0

replied on October 22, 2014

Okay, I got the repository working with SQL Server Authentication. Looks like SQL 2012 R2 shipped with that login mode off for whatever reason. Thanks for the help guys.

0 0

replied on March 14, 2016 • Show version history

I just had this same error as well. I found this article while looking for the answer. What happened in my case, I used a random password generator to create the SQL password. I could log into management studio just fine, but Laserfiche wasn't happy passing the password along. When I removed these characters, ( } from the password, then Laserfiche would carry on to accessing the db.

0 0

You are not allowed to follow up in this post.

Question

Question

SQL Native client 2005 not installed: continued

Replies

Sign in to reply to this post.