Jump to content
  • 0

Server closes when attempting to update databases (Upgrade)


PrincessNoodlelimbs
 Share

Question

Hi all

 

I'm having an issue with Upgrading to the latest (and several of the previous) version of Intersect. I'm trying to Upgrade from 0.6.2.460 to the latest version (0.7.1.98) - although once I encountered this error I tried the three versions previous to it, too, and had the same problem.

 

The problem description is pretty simple. I make a backup, create a new folder, drop the old folders into the new folder. Then I drop the Upgrade folders into the folder and select Replace the old files, just like any other Upgrade I've done in the past. It's always worked before. When I start up the new server, I get the usual "Your databases need to be updated" message, and I type READY and hit Enter. The server window displays the "Please Wait" message, pauses for a few seconds, then closes. That's it. When I try again, same thing except it closes immediately instead of pausing and displaying the "Please Wait" message. 

 

So basically, the server tries to update the databases as usual, but crashes pretty much immediately. This happens every time I try it.

 

Here's the server log file: https://www.ascensiongamedev.com/resources/filehost/d917915f6127922d8bae3e98438daebd.log

Edited by PrincessNoodlelimbs
Added latest server version
Link to comment
Share on other sites

7 answers to this question

Recommended Posts

  • 0

Being completely honest I'm going to need to run the upgrade on your DB through the debugger because while I know what is failing I do not know why, but I also don't have time to do that right now (since I can't even build B7.1 on my computer right now, I will need to fix that first).

As an interim solution/test can you try upgrading to 0.7.1.74-beta instead? The log is complaining about something introduced in .75-.77 so I would expect .74 to work (or produce a different error).

Also just to be sure, have you only ever used the stock builds that we provide, or have you made source code modifications?

Link to comment
Share on other sites

  • 0
14 hours ago, PrincessNoodlelimbs said:

Hey, happy to say that upgrading to 0.7.1.74-beta works fine. No server crash issues. 

 

And yeah, I've only ever used stock builds. 

 

Can you check if you can upgrade beyond .74 now? I wonder if the way migrations are applied that a straight upgrade from 0.6 can't go to .77+.

Link to comment
Share on other sites

  • 0
18 minutes ago, PrincessNoodlelimbs said:

Tried upgrading to .98 from .74, server crashes on updating database again.


Can you upload the logs? (If they don't tell me enough I may also end up asking you to DM me a copy of your DBs but uploaded via something that allows you to delete the file, which the AGD file host does not.)

Link to comment
Share on other sites

  • 0

Sure. Here's errors-Intersect Server.log: https://www.ascensiongamedev.com/resources/filehost/a1f6b517f3ddba2fcf25fd8e278dc126.log

 

And here's playerdbIntersect Server-2023_01_25-11_26_07_738.log: https://www.ascensiongamedev.com/resources/filehost/5e0807523b2ab6c09ad0b3fe576e11ab.log

 

I would upload Intersect Server-2023_01_25-11_26_07_738.log, but literally all it says is "[Error] Received unhandled exception from System.Threading.Thread."

Link to comment
Share on other sites

  • 0
2 hours ago, PrincessNoodlelimbs said:

Sure. Here's errors-Intersect Server.log: https://www.ascensiongamedev.com/resources/filehost/a1f6b517f3ddba2fcf25fd8e278dc126.log

 

And here's playerdbIntersect Server-2023_01_25-11_26_07_738.log: https://www.ascensiongamedev.com/resources/filehost/5e0807523b2ab6c09ad0b3fe576e11ab.log

 

I would upload Intersect Server-2023_01_25-11_26_07_738.log, but literally all it says is "[Error] Received unhandled exception from System.Threading.Thread."


Ok, unfortunately the logs aren't giving me a hint as to why the SQLite migration is failing on your PlayerDB.

If you could send me a copy via a more private upload (honestly if you wanted you and the playerdb is under 20MB you could use email and send to my public email listed on GitHub, pandacoder@pm.me) I can see if I can figure out what is going wrong.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...