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

Question

Question

I am unable to view and migrate LF 7 repository in the migration wizard

Updated March 18, 2014
asked on March 17, 2014

I am migrating a repository from LF 7.x to 9.x.  I have successfully migrated 4 of 7 repositories.

 

The SQL database for the successfully migrated repositories were located on one of our SQL servers.  The problem repository is the original repository and the database is still located on the local version of SQL on the LF 7.x server.  The database does not show up in the Laserfiche Migration Wizard on the Source SQL Server specific settings dialog box.  How do I migrate a database located locally on the Laserfiche 7.x server.

 

0 0

Replies

replied on March 17, 2014

I guess the question to ask is .... does the migration utility work with what ever version of SQL that existed on a 7 year old windows 2003 server.

 

0 0
replied on March 18, 2014

Migration utility support migrate from SQL 2000(full version and SQL Express(MSDE)) or above. Please check the name in the "()" after the SQL Server in the local services list. Then set the sql server name as  "machine_name\name_in_the_brackets" on migration wizard. For example: if the service name is "SQL Server(SQLExpress)", the SQL server name set on the wizard should be servername\sqlexpress.

0 0
replied on March 18, 2014

This is on a Windows 2003 server

The name listed in the Services window is just: MSSQLSERVER

The name listed in the services tab in Task Manager is: sqlservr.exe

The program listed in Add or Remove programs is: Microsoft SQL Server 2000

 

I do not see any brackets as described above.

 

I am guessing I just have an incompatible version for the migration or I am just looking in the wrong places.

 

what next?

 

 

 

 

0 0
View 1 previous reply
replied on March 18, 2014 • Show version history

Are you running group server with an instance?  Like Xiuhong said, try putting the SQL instance name after the server name.  

 

servername\instancename

 

Again you will only need this if your database is in an instance or on team/group server.  

 

Try taking Laserfiche (the migration wizard) our of the equation.  

 

Open SQL Management Studio and connect to the SQL server that your database is located.  What is the server name at the connection prompt?  Of course you need to connect to the correct SQL server and the right instance (if you have an instance).  

 

Once you connect, can you see the Laserfiche database in the database node?  If you can see your Laserfiche database in the database node, then the server name in the box before you connected is the one you want to use for during the migration wizard.

 

Also take note of the credentials you use when you logged into SQL Management Studio.  Did you use Windows Authentication or credentials of some kind?  Use the same info in your Migration Wizard that you did to successfully get to the database in the Management Studio.  

0 0
replied on March 18, 2014

I had my SQL guy come over.  it is just a single database in SQL 2000.  He was not able to get it to connect or find the DB.  We backup up the database and restored it to one of his SQL servers.  I was able to connect and find the DB on his server.  it is migrating.  We don't see any reason this shouldn't work.

 

I will post again when it competes and I test the migration.

 

0 0
replied on March 18, 2014

Sounds like the database maybe was not attached or something was wrong with it.  If you restored it to a SQL server and can hit it via the Management Studio the migration should be fine.

0 0
replied on March 18, 2014

There could also just be a security issue. Maybe the SQL Server on this one machine isn't set up to allow external communication. That said, if you can restore it on another Server and that works, you should be fine just using that anyway.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...