Request for Character and ItemsStorage Database Backups

Newbie Spellweaver
Joined
Nov 2, 2026
Messages
8
Reaction score
0
Hello,


I'm currently setting up an A3 game server using the A3 Server 219 files.


I have several database backups, but I'm missing the original Character and ItemsStorage database backups.


If you still have these files, could you please share them?


My current environment is:


  • Windows 7 64-bit
  • SQL Server 2005 Developer Edition SP4

I'd also appreciate information about the original server version, client version, and SQL Server version used with these databases.


I'm looking for the original, unmodified backup files.


Thank you for your help!
 
In my experience those 2 databases are never used by any executable. Did you try creating those databases and start OBDC stage? That should just work in my opinion.
 
In my experience those 2 databases are never used by any executable. Did you try creating those databases and start OBDC stage? That should just work in my opinion.
Thank you for your advice.


We are currently stuck at the ODBC connection stage.


Here is our current environment:


  • Windows 7 64-bit VM
  • SQL Server 2005 Developer SP4
  • SQL Native Client 9.0 (32-bit)
  • A3 Server 219 package
  • 32-bit System DSNs h3db00 through h3db15 have been created.

Our current database situation:


  • The database asd exists and is ONLINE.
  • asd contains the tables account, charac0, and ItemStorage0.
  • The databases Login202 and NEWASD do not currently exist.

The middleware configuration files specify:


  • Port 7770: Login202 / account
  • Port 8880: NEWASD / charac0
  • Port 9990: NEWASD / ItemStorage0

Individual ODBC connection tests using SQL Native Client 9.0 are successful, but when we run the middleware, all 16 DSN connections fail.


SQL Server error logs show login failures for sa, error 18456, State 8.


Both middleware versions (v1.1.19a and v1.3.21a) produce the same result.


My questions are:


  1. Should we create separate databases named Login202 and NEWASD and restore the appropriate backups into them?
  2. Or should all three middleware services connect to the existing asd database?
  3. Is there a specific database creation or initialization script required for A3 Server 219?
  4. Could the middleware be parsing the password incorrectly, especially since the password in our configuration starts with @?

I would appreciate your guidance on the correct database structure and ODBC configuration for this server package.
 
Thank you for your advice.


We are currently stuck at the ODBC connection stage.


Here is our current environment:


  • Windows 7 64-bit VM
  • SQL Server 2005 Developer SP4
  • SQL Native Client 9.0 (32-bit)
  • A3 Server 219 package
  • 32-bit System DSNs h3db00 through h3db15 have been created.

Our current database situation:


  • The database asd exists and is ONLINE.
  • asd contains the tables account, charac0, and ItemStorage0.
  • The databases Login202 and NEWASD do not currently exist.

The middleware configuration files specify:


  • Port 7770: Login202 / account
  • Port 8880: NEWASD / charac0
  • Port 9990: NEWASD / ItemStorage0

Individual ODBC connection tests using SQL Native Client 9.0 are successful, but when we run the middleware, all 16 DSN connections fail.


SQL Server error logs show login failures for sa, error 18456, State 8.


Both middleware versions (v1.1.19a and v1.3.21a) produce the same result.


My questions are:


  1. Should we create separate databases named Login202 and NEWASD and restore the appropriate backups into them?
  2. Or should all three middleware services connect to the existing asd database?
  3. Is there a specific database creation or initialization script required for A3 Server 219?
  4. Could the middleware be parsing the password incorrectly, especially since the password in our configuration starts with @?

I would appreciate your guidance on the correct database structure and ODBC configuration for this server package.
Are all the ODBCs created correctly? You can try to use https://forum.ragezone.com/threads/omnihance-web-based-server-management-tool.1257629/ tool to create ODBC automatically if things are missing. Share error screenshots.
 
Hi cyberinferno,


Thank you for developing and sharing Omnihance. I'm currently restoring an A3 Server 219 (Episode 5) environment on a Windows 7 64-bit VM with SQL Server 2005 SP4.


I'm having trouble connecting the A3 middleware to SQL Server, and I noticed that Omnihance includes automatic A3 SQL Server DSN creation.


Here is my current situation:


  • SQL Server 2005 Developer SP4 is installed and running.
  • SQL Native Client 9.0 (32-bit) is installed.
  • I created all 16 System DSNs (h3db00–h3db15) using the 32-bit ODBC administrator.
  • Individual ODBC connection tests are successful using SQL Server authentication with sa.
  • However, the 7770 middleware (asd_mw_v1.1.19a and v1.3.21a) fails to connect to all 16 DSNs.
  • SQL Server error logs show login failure 18456, State 8, for sa.
  • The password in my middleware configuration starts with the special character @.

My tdb.ini files specify:


  • Port 7770: Login202 / account
  • Port 8880: NEWASD / charac0
  • Port 9990: NEWASD / ItemStorage0

Currently, the database named asd exists and contains all three tables with data, but separate databases named Login202 and NEWASD do not exist.


Could you please clarify a few things?


  1. Does Omnihance create the required A3 DSNs as 32-bit System DSNs or User DSNs?
  2. Does its DSN creation feature support the h3db00–h3db15 naming scheme used by this middleware?
  3. Is it possible that the middleware cannot parse passwords beginning with @ correctly?
  4. For A3 Server 219, should Login202 and NEWASD be separate databases, or should both point to the existing ASD database?

Any advice on the correct ODBC configuration or database structure would be greatly appreciated.


Thank you!
 
Hi cyberinferno,


Thank you for developing and sharing Omnihance. I'm currently restoring an A3 Server 219 (Episode 5) environment on a Windows 7 64-bit VM with SQL Server 2005 SP4.


I'm having trouble connecting the A3 middleware to SQL Server, and I noticed that Omnihance includes automatic A3 SQL Server DSN creation.


Here is my current situation:


  • SQL Server 2005 Developer SP4 is installed and running.
  • SQL Native Client 9.0 (32-bit) is installed.
  • I created all 16 System DSNs (h3db00–h3db15) using the 32-bit ODBC administrator.
  • Individual ODBC connection tests are successful using SQL Server authentication with sa.
  • However, the 7770 middleware (asd_mw_v1.1.19a and v1.3.21a) fails to connect to all 16 DSNs.
  • SQL Server error logs show login failure 18456, State 8, for sa.
  • The password in my middleware configuration starts with the special character @.

My tdb.ini files specify:


  • Port 7770: Login202 / account
  • Port 8880: NEWASD / charac0
  • Port 9990: NEWASD / ItemStorage0

Currently, the database named asd exists and contains all three tables with data, but separate databases named Login202 and NEWASD do not exist.


Could you please clarify a few things?


  1. Does Omnihance create the required A3 DSNs as 32-bit System DSNs or User DSNs?
  2. Does its DSN creation feature support the h3db00–h3db15 naming scheme used by this middleware?
  3. Is it possible that the middleware cannot parse passwords beginning with @ correctly?
  4. For A3 Server 219, should Login202 and NEWASD be separate databases, or should both point to the existing ASD database?

Any advice on the correct ODBC configuration or database structure would be greatly appreciated.


Thank you!
Login202 and NEWASD are ODBC names. Omnihance auto-creates required ODBC entries under ODBC 32Bit user DSN as required by the exe files.
 
Back