SQL Migration Fails

 
Author
Message
EJB
SysAider
10
 
Now I keep getting the must restart prompt when trying to install the sysaid 14.1 patch. I've restarted 5 times and it keep getting it.
EJB
SysAider
10
 
Okay finally got it to migrate. Was having trouble with the creating the sysaid database part right before the migration starts. Not really familiar with SQL but figured it out in the end.

Hopefully 14.1 solves the issue we've been having with derby throwing database errors.
Former Community Manager
980
 
Hi EJB,

Glad to hear you finally made it to 14.1. I'm very curious to know if the change to MS SQL takes care of the Derby errors. SQL certainly is more robust for production and should provide a more stable and efficient backend for the database.

Michael
SysAid Customer Relations
76
 
Hi everyone,

Before upgrading to 14.1 with a Derby database you need to make sure there are no MSSQL instances installed on your server. If there are Go to Add/Remove Programs and uninstall it.
Also go to your Program Files folder and make sure you don't have a 'SysAidMsSql' folder. If there is, delete it.

Finally, if you have a Derby database you can only upgrade to version 14.1 from version 9.1. Make sure you have the correct version by clicking your username at the top right and selecting 'About.
If your version is lower than 9.1, click this link to download the upgrade patch to 9.1 for your server.

I hope this helps.

Kobi Versano
SysAid Customer Relations
EJB
SysAider
10
 
Kobi Versano wrote:Hi everyone,

Before upgrading to 14.1 with a Derby database you need to make sure there are no MSSQL instances installed on your server. If there are Go to Add/Remove Programs and uninstall it.
Also go to your Program Files folder and make sure you don't have a 'SysAidMsSql' folder. If there is, delete it.

Finally, if you have a Derby database you can only upgrade to version 14.1 from version 9.1. Make sure you have the correct version by clicking your username at the top right and selecting 'About.
If your version is lower than 9.1, click this link to download the upgrade patch to 9.1 for your server.

I hope this helps.

Kobi Versano
SysAid Customer Relations


I had 9.1 installed and no MS SQL and still had issues upgrading to 14.1. Fairly annoying to jump through hoops just to get it to migrate.
SysAider
13
 
Yes, as mentioned in one of my earlier posts I also installed 9.1 on a freshly built machine with no prior SQL and was still unable to migrate without problems. Can't really complain though as I'm on the free version and not paying for anything.
SysAider
22
 
I'm having the same troubles and we are not using the free version. I don't get a freeze at the migrating database stage so there is no time to install the extra software as a workaround. Once it tries to install MSSQL Express it pops back to the sysaid installation window saying migration failed. After clicking ok it proceeds to back out the MSSQL express installation and not install the update. We are pretty much just stuck at this point. Hoping for an update soon.
Former Community Manager
980
 
Hi savardm,

Have you checked the derbytomssqlmigration.txt file located in the logs directory? The file can usually be found under c:\program files\sysaidserver\root\web-inf\logs and may contain additional information as to why the migration failed. For users of the free edition, there's an error that the destination database "sysaid" could not be found. Do you see a similar error in your logs?

Thank you.

Michael
SysAider
9
 
I am having the exact same problem. The installation starts, the migration begins and immediately fails.

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

Former Community Manager
980
 
Hi areiner,

What does the derbytomssqlmigration.txt show? If you can post the contents, that can help find the issue.

Thank you.

Michael
SysAider
9
 
There is no such file. It doesn't get that far.
Removed everything SQL related from the server, no change.
I did notice that the mongoDB service was running as well.
Disabled it and removed the directory, no change.
Disabled the SysAid service, no change.

System is:
MS Server 2008 x64

SysAid: x86
Application Server: Apache Tomcat/6.0.26
SysAid Edition/Package: PackagePro Edition
Build Number: v9.1.02 b71
Database Vendor: Derby

This message was edited 2 times. Last update was at Apr. 11, 2014 07:26 PM

Former Community Manager
980
 
Hi areiner,

The mongoDB is only for logging. You shouldn't have to disable the other services since they may be required by the install to run.

At this point it may be best to contact our support group to help, especially since there are no logs being generated from the failure. There could be another issue going on that's causing the migration to fail. If you need any assistance with contacting support, feel free to send me a private message or email and I'll get you in contact with the right people.

Michael
SysAider
9
 
I had already contacted support. I am still in contact with them. I will update with whatever fix we find just in case this applies to someone elses problem as well.

Recap of my efforts so far:

Attempted the update and it failed on migration immediately after starting migration.
After several tries, I created a new server, copied the SysAidServer directory to it, copied the backed up database and ran the installer for 14.1. Migration is now successful but the SysAid service will not start. It crashes with an error.
Completely removed SysAid, removed SQL, rebooted.
Installed version 9 from a link provided by support.
Provided it with the activation key it asked for and the service ran properly.
Installed the 9.1.02 patch and the service starts normally.
Stopped the service manually.
Copied the database backup and various xml files back into the directory.
Attempted to start the service and it stopped immediately again.
Rebooted the system (service still stopping immediately) and attempted the 14.1 upgrade with the same results. Service starts then stops immediately.

Edit: Made a slight error in writing down what my process was. Corrected it for accuracy.

This message was edited 1 time. Last update was at Apr. 14, 2014 05:02 PM

SysAider
9
 
The problem turned out to be with the original server.xml file in the tomcat\conf folder. I discovered that the replacing that file with the one I had backed up was causing the service to fail. There was a difference in the size of the backup file vs the freshly installed file.

I removed all remnants of both programs again(SQL and SySAid).
I reinstalled version 9.0.533 from this https://cdn3.sysaid.com/SysAidServer.exe.9.0.533 and the service started okay.
I made a backup copy of the \root and \tomcat folders.
I upgraded to v9.1.0.2 b71 and the service started okay.
I made another backup copy of the \root and \tomcat folders.
I stopped the service and restored the backup files for the database and various configuration xmls.
I started the service and the service failed.
I started checking the xml's against each other and discovered the size difference.
I replaced the \tomcat\conf\server.xml file with the backup copy from the v9.0.533 backup and the service started normally.
I performed the upgrade and it migrated successfully, the service started successfully and I can access SysAid again.
I am no back to my original problem which had nothing to do with the upgrade and am waiting for the call from tech support.

I have no idea if this will be helpful to anyone or not but there it all is. I will include a copy of the two flies as an attachment to the tech that is helping me.
Good luck all.
mks
SysAider
22
 
has Sysaid not got a fix for this problem yet ?

I get the failed message as soon as the migration starts.