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

Question

Question

Upgrade sql native client when moving databases to sql 2012?

Laserfiche Version 8 Installation and Upgrades
Updated February 5, 2015
asked on October 6, 2014

A client has built a new sql 2012 cluster and intends to move their existing sql 2008 DBs to it. Does anything need to be done with the databases for Laserfiche to be compatible (e.g. upgrade the Laserfiche server native client from 2005 and/or change the compatibility on the db, etc)?

 

They are currently running server 8.3.2 and plan to upgrade to 9.1 in the coming months.

Thanks,

Micah

 

 

0 0

Answer

APPROVED ANSWER
replied on October 6, 2014

The SQL Server 2005 Native Client will work fine with SQL Server 2012. The Native Client is required as it contains the SQL ODBC driver.

0 0

Replies

replied on October 6, 2014

You can take the SQL 2008 databases and attach them to SQL 2012. The conversion should be handled automatically.

As for the SQL Native Client, Laserfiche 9.1 and earlier needed to use SQL Native Client 2005 in order to create/register repositories using the wizard. There was also an issue where the SQL Native Client wouldn't function properly if there were other versions of the SQL Native Client installed on the same computer.

Laserfiche 9.2 now uses SQL Native Client 2008 R2 and there should be no conflicts if other versions of the SQL Native Client are also installed.

0 0
replied on October 6, 2014

Thanks Alex.

One more thing... this client is claiming that sql native client 2005 will not work with sql 2012. Your response seems to indicate that 9.1 and lower requires native client 2005. I assume they are incorrect, but are there any concerns here? 

 

On the other hand, if they will not register any more repositories with the wizard, no native client is needed for Laserfiche server to function?

 

Thanks again,

Micah

0 0
replied on October 7, 2014

Thanks for the response.

0 0
replied on February 4, 2015

OK all,

I've got this fresh install of Avante 9.2 on a dedicated Server 2012 R2 VM that's at the stage where I'm trying to create a repository using the wizard. I have a SQL Server 2012 Always On Availability group set up and ready to receive connections, but the Repository Creation Wizard can't seem to find my listener. The listener is registered in the local DNS, the repository server can find it in an nslookup, and I've even tried referring to the SQL server AAG listener by its static IP address, all with no success. So two questions fall out of this when I shake it:

1. Which SQL native client is required with Avante 9.2? 2005 or 2012. I've tried both and with both I get this error 9025 in the Repository Configuration Wizard about the 2005 native client not being installed, which seems to come from some database configuration problem. Do I need some other version of the native maybe, or is this error from something else?

2. Is an Always On Availability Group even supported with Avante 9.2? Has anyone successfully set up Avante against a SQL Server 2012 AAG?

Any thoughts, I'm all ears - Dale.

0 0
View 2 previous replies
replied on February 4, 2015 • Show version history

The repository wizard that ships with Laserfiche 9.2 requires SQL Server Native Client 2008 R2. This version of the native client should be installed automatically when you install the Client suite with the Administration Console. However, if that's not the case, then you can manually install it by browsing the 9.2 installation files and installing sqlncli_amd64.msi located in the en\Support folder.

0 0
replied on February 5, 2015

Yes, the 2008 native client appears to be installed. I've tried the 2012 ncli, the 2005 ncli, uninstalling the others and restarting as I go, and I'm back to the just the 2008 ncli. The Repository Creation Wizard appears to still not be able to connect to the SQL Server AAGL I created for my Laserfiche databases.

Now I'm getting '9025 - Error reading repository information, or the repository is misconfigured.' and the Windows application logs is saying 'Repository creation error. Invalid connection string.' 

All of this looks like the Wizard just isn't able to connect to SQL Server. These servers are all members of the same domain, same subnet even. Using a domain account with lots of permission to do stuff.

Not sure what to do from here.

0 0
replied on February 5, 2015

From the Laserfiche Server computer, are you able to log into the SQL instance using SQL Server Management Studio? If so, note the SQL instance name as well as whether you had been using Windows Authentication or SQL Authentication.

Next, in the repository creation wizard when specifying the SQL information, make sure to use the same instance name that was used in SQL Server Management Studio. If you decide to use Windows Authentication, make sure that the Laserfiche Server service is configured with an account that has access to SQL, perhaps even the same account you're currently logged into Windows with and had seen work fine in SSMS, if only to test. If you decide to use SQL Authentication, try using the same account that you used in SSMS.

Complete the repository creation process and if you are still getting an error message, then please contact your Laserfiche reseller to open a support case so we can investigate this further.

0 0
replied on February 5, 2015

OK, that's interesting. I changed the Laserfiche server service account to one that's known by SQL Server, and I'm still getting the 9025 error, which must be the all purpose database connectivity error, but now the Windows Application log says the 'named user account license database could not be opened'. This error seems more like a licensing problem than a plain old can't connect error.

0 0
replied on February 5, 2015

Does the account that's running the Laserfiche Server service have access to the lfsnu.db file which would be located in the Laserfiche Server program files folder?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...