Hi.

A Rio client would like to have a separate test repository set up using a copy of the Production repository.

They have backed up the Production database and restored it to a new SQL 2014 server under a different name than the db name being used in Production. The test database is attached and the SQL services are running.

They have copied all the repository folders and files from Production to the test server which has a Windows 2012R2 OS.

Today we installed the Laserfiche server and client software on the test server and then attempted to run the 64bit version of the UUID update utility on the copy of the database but it failed with the error message "Unable to connect to the SQL database". This happened when using the Windows authentication option or when using the SA username and password option in the UUID update utility.

The Laserfiche server service is running under a domain account with local admin rights and this account has the DB Owner permission in the test database (basically the same settings that are being used in Production).

The servers are all on the same network and can see each other (ie we can ping the SQL2014 server from the Laserfiche test server). As a test the IT admin disabled the Windows firewall for all ports.

After filling in the database server name field in the UUID update utility then tabbing to the database name field an error saying that the "sql server native client isn't installed" is displayed but we did install the 2008 version when we installed the Laserfiche server software. This is full sql by the way.

We then attempted to run the UUID update utility right on the SQL 2014 server and experienced exactly the same errors.

I saw another post about a different UUID-related problem and the solution appeared to be to install sql server native client 2005 because 2008 didn't work. Would this be the case here as well? Is the UUID utility compatible with SQL Server 2014?

I also saw an answer to a different post which said that if the Production database has been copied to a different SQL server and the volumes have been copied to a different server then the UUID utility doesn't have to be run. Would it be safe in the case I have outlined above to just go ahead and register the test repository without running the UUID update utility? Is there any way that this could negatively impact the Production environment?

Any assistance would be greatly appreciated!

Thank you,

Rob

Just to follow up -  "if the Production database has been copied to a different SQL server and the volumes have been copied to a different server then the UUID utility doesn't have to be run". This was indeed the case. The test repository is in place and working.