SQL Migration Fails

 
Author
Message
SysAider
13
 
Hi all,

I'm currently trying to upgrade from v9.1.02 b71 to 14.1, running on Server 2003.

The installation package identifies that I'm running the Derby database and attempts to migrate it to the embedded MS SQL Express database. It keeps failing at this point though and just reports "migration failed'.

Has anyone else experienced this problem and been able to resolve it?

There was a redundant application on the server that was using SQL Express 2008 which has been removed to avoid sharing conflicts with 2008 R2 Express. The only other application on the server that relies on SQL is Backup Exec which runs SQL 2005.

There are various SQL logs generated which I've looked through, but I've been unable to diagnose the cause of the failure. If anyone can suggest which log should be examined I can post it.


Cheers,

Matt

This message was edited 1 time. Last update was at Apr. 01, 2014 01:09 PM

EJB
SysAider
10
 
I'm in the same boat. I found the log in C:\Program Files\SysaidServer\root\WEB-INF\logs. Its a file called "derbyToMssqlmigration.txt". My migration either fails or hangs and haven't found a solution as to why. Sysaid won't help because I'm on the free edition.
SysAider
13
 
Yes I'm also on the free version and unable to get support from Sysaid. I'm contemplating installing v9.1.02 on a different server, importing my backup and trying to migrate on that server.

I've got a feeling it must be something to do with shared SQL services on my current server. I'll check out that log you mentioned though, I hadn't seen that.
SysAider
13
 
I've got to the point now where I've resigned myself to the fact that if I want to run 14.1 it's going to have to be from scratch losing all my previous history and configuration, the migration process is clearly flawed.

I've just:

- Installed the only full Sysaid installation package I had which is v6 on a freshly built test machine
- Patched it up to v9.1.02
- Restored my backup

Now when trying to upgrade to 14.1 it just hangs on "starting the migration process". It's been like that for the last 30-45 minutes.
rt
SysAider
2
 
Are you sure the database didn't migrate, It looks as though my upgrade stalled but it actually did migrate the database it just did not install sysaid 14.1. Now if I try to use the upgrade patch it tells me that the mssql has been installed and then ends the upgrade.
SysAider
13
 
I did end the migration process via the task manager so that it wouldn't roll back the SQL install. When I tried to run the upgrade again, I got a message saying the SQL service was already installed, I gave up for the day at this point though.

Without installing Studio Management and logging in to the database I'm not sure what is in there, I''ll take a look tomorrow, cheers for the tip.
Former Community Manager
980
 
Hi mkoopa,

I did find a solution that seems to work, albeit it does take a little bit of timing.

Here are the steps that worked for me:

1. Make sure MS SQL 2008 R2 Express is uninstalled. If you forced the installer to quite while at the "Migrating database" screen, after SQL Server installation, then you will definitely need to uninstall the SQL server.

2. Go to Microsoft's site and download Microsoft SQL Server 2008 R2 Management Studio Express at https://www.microsoft.com/en-us/download/details.aspx?id=22985. Make sure you download the 32-bit edition to match SysAid free edition.

3. Once MS SQL 2008 R2 Express is uninstalled, install the patch again. Let the SQL Server installation complete and wait for it to freeze at the "Migrating Database" screen. When this occurs, DO NOT cancel. Instead, install the Management Studio Express as you downloaded in step #2.

4. Once Management Studio Express is installed, you should see that you can connect to the SQL server, even while the SysAid updater is still frozen. When you connect, you can view the databases. Take note that there is not a database named sysaid.

5. Go back to the SysAid update, and cancel the installation. SQL Server Express will uninstall itself. This is ok, as the Management Studio will stay on your computer.

Here comes the tricky part...

6. Run the SysAid update again. Let MS SQL Express R2 install as before. As soon as it completes, and before the installer switches back to the database migration, open Microsoft SQL Server Management Studio and right-click on "Databases." Left-click on "New Database..." Under "Database name" type in "sysaid." Under "Owner," enter in "sa" and then push "OK" at the bottom to create the database. (see attachment for a screenshot of what it should look like).

7. If you time it correctly, as soon as the migration begins the update application will find the sysaid database in MS SQL and continue the migration. Once the migration is complete, the update will continue and you'll be on version 14.1 (yay!).

Some things to note:

1. I reproduced this problem by first installing MS SQL Express 2008 R2 before installing 9.0, or the update to 9.1. I haven't confirmed if this is a bug from simply updating 9.1 to 14.1, or if it's related to having MS SQL already installed.

2. If you already are using an instance of MS SQL Express 2008 R2 for other applications, then you'll never get past the "SQL is already installed" error. If you really need to maintain the SQL server, I recommend to contact our support team to help with the migration. The only way I can think to do it would be to migrate SysAid to another server, perform the upgrade, detach the newly migrated database, move everything back to the original server and attach the SQL database back to SQL Express. And then update the server configuration settings to make sure the database setting is correct.

I hope these steps help you with your upgrade. 14.1 really does have some nice features and the upgrade to SQL will only help for us to keep improving on the platform.

Cheers,

Michael
SysAider
13
 
Thanks for your post Michael, there's some good information there. I wouldn't have thought about trying that.

My plan was as you suggested to migrate it to 14.1 on my test machine. Install a fresh install of 14.1 from the full installation file on my orginal server then copy across and attach the SQL database.

Hopefully I'll be able to migrate via your suggested method.
SysAider
13
 


That has worked Michael......it's finally migrated!!

I just need to get the new database up and running on my server now, then should be all good. If it wasn't for the migration hanging this process wouldn't have been possible as on my server the migration stage just failed instantly.

Thanks for the help!
EJB
SysAider
10
 
I tried this method and it won't let me install SQL 2008 r2 management. Gets stuck at the selecting features part.
Former Community Manager
980
 
Hi EJB,

Can you post a screenshot of where the manager installation gets stucks? It's not the most straightforward install and I had to spend some time navigating it myself.

Thanks.

Michael
Former Community Manager
980
 
Hi Everyone,

I can confirm that this bug does occur on updating to 14.1, even without SQL being previously installed. We'll see if we can get this resolved soon.

Thank you for your feedback and patience.

Michael
EJB
SysAider
10
 
This is what happens when I try to install SQL Manager while the Sysaid installer is stuck at "Starting Migration". I tried both new installation and add features to an existing instance of SQL.
SysAider
13
 
I installed the studio management software before starting the sysaid upgrade. At the point of the migration hanging you should be logging in to the studio manager and manually creating the sysaid database.

This message was edited 1 time. Last update was at Apr. 04, 2014 07:07 PM

Former Community Manager
980
 
I had to install the studio management software right in the middle of the upgrade; when the SQL Server installed, but before database migration.

Another option is to install MS SQL Server 2008 R2 Express first, then install the studio management software. Once the studio software is installed, then uninstall SQL Server 2008 R2 Express in Add/Remove programs.

Michael