You are viewing limited content. For full access, please sign in.

Question

Question

SQL Native client 2005 not installed

asked on April 21, 2014

I am installing Laserfiche 9.1 server on a Windows 2012 R2 server running SQL 2008 R2 locally.  The server prereqs are satisfied (yes, even SQL Server 2005 Native Client).  Yet when I attempt to attach the existing repository it will not allow me past the SQL server connection part of the wizard.  It gives me the error that SQL Native Client 2005 is not found.

 

I have uninstalled the SQL Native Client, and re-installed from the LF install.  Still no luck.

 

Does any type of backwards compatibility need to be installed, extra services? 

 

Answer

APPROVED ANSWER
replied on April 22, 2014

For this specific issue, it was preventing the repository from registering. After uninstalling all installed versions of the SQL Native Client from the server and then only installing the version that ships with Laserfiche 9.1.1, the repository was able to get registered when manually specifying the SQL instance and using Windows Autentication to connect. 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. After detaching the database from the old SQL instance and attaching it to the new instance, there were no issues.

Replies

replied on April 22, 2014

Are you attaching the repository using a LF Admin Console on the same machine as the LF Server?

replied on April 22, 2014

I am.  Would it be better to do it from a different machine?

replied on April 22, 2014

No, the same machine should be fine. But that could've been one of the causes if you only had the Admin Console on a machine without SQL Native Client.

 

Did you install the x86 or the x64 version of SQL Native Client? The Admin Console defaults to installing as x64 on Windows 2012 R2, so it wouldn't detect a x86 version of SQL Native Client.

replied on April 22, 2014

SQL 2005 Native Client (x64) doesn't work.... Also tried the December 2008 version and the latest SP4 version. 

 

I also rebooted after installing them (even though not required). Laserfiche prompts this when trying to expand the "Server" drop down list for the SQL Server Specific Settings page.

 

Its installed though!

replied on April 22, 2014

If you manually type in the SQL instance name, are you able to select the database from its drop down list? If not, confirm what authentication type you're using to connect to SQL. If the authentication method should be valid and the user should have the necessary rights, but there's still an issue, then open a case with Laserfiche Support.

replied on April 22, 2014 Show version history

I did manually and it let me proceed but then got a "9004 File input/output error" when trying.

 

I tried both Windows and SQL Authentication. The accounts are sysadmins on the SQL server and I even logged into the SQL server using SQL Management Studio using the same values I was putting into Laserfiche

 

After logging in with SQL Management Studio I verified that I did have rights to everything (create, delete, etc).

 

*EDIT* Also: No it wouldn't pull the databases but I was trying to type it in manually (listed above is what happened when I continued)

replied on April 22, 2014

Please open a support case so the issue can be further looked into.

APPROVED ANSWER
replied on April 22, 2014

For this specific issue, it was preventing the repository from registering. After uninstalling all installed versions of the SQL Native Client from the server and then only installing the version that ships with Laserfiche 9.1.1, the repository was able to get registered when manually specifying the SQL instance and using Windows Autentication to connect. 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. After detaching the database from the old SQL instance and attaching it to the new instance, there were no issues.

You are not allowed to follow up in this post.