"Invalid auth. error" when connecting over LAN

[topherdan]

Hello All,

I have a multi-user database I'm trying to deploy over a LAN at my office. I have another (very similar) version running successfully on other computers on the same network, but when I tried to set up the new one I receive errors ("invalid authorization specification") when trying to connect from computers other than the one the server is running on.

There are a number of differences between the two systems that may be causing me problems, but I don't have enough experience to know the ins and outs. Here's a brief summary:

BOTH databases are running HSQLDB 2.2 in server mode.
The correctly working database is running the server on a computer with Windows XP and OpenOffice 3.3. Connecting computers are using Windows 7 and OpenOffice 3.4.

The new, not yet working database is running the server on Windows 7 with OpenOffice 3.4. The database file on this computer connects to the server using the computer name (even though it is running on the same computer, ie. I'm not using the localhost address to connect). Connecting computers are using an identical database file with the user name changed (I created users using the database on the working computer) but I'm getting errors when trying to connect.

Does anybody know of any idiosyncracies (especially with regard to running an HSQLDB 2.2 server on Windows 7) that may be helpful for me?

Thank you for any help you can provide!
Chris

[DACM]

Hmmm...

I'm not familiar with that error, but here's what I would do to troubleshoot the issue:

(1) Make sure the database folder is shared among all clients at the operating system level. Windows 7 employs more robust security than XP so make sure you can read and write to perhaps other files within the database folder from clients on the host machine. For instance, place a text file in the database folder and make sure you can open it and save edits without issue from the clients.

(2) Make sure the clients have the same version of HSQLDB (hsqldb.jar). Your signature currently indicates OOo 3.3. Make sure each installation of OOo 3.3 is configured to use HSQLDB 2.2.x. You can set this up manually through Tools>Options>Java>Class Path. If you're using the Windows installer (OOo_hsqldb2.exe) to setup HSQLDB 2.2.x on each machine, then that will work with OOo 3.3, but I'm noticing that I need to make a new installer to accommodate AOO 3.4 and LO 3.5.x because the name and location of the .ini file has changed to: ...\program\fundamental.ini[/b].

[topherdan]

Thanks for the response!

I currently have the DB files stored at the root level on the server computer, which is likely causing the problem (I don't have it in front of me at the moment so I can't check). The computer in question is in Japanese, so I sometimes have problems finding options - in order to make a public folder, do I just edit the properties of the folder? (newbie question, I know).

I also ran the old installer with the AOO 3.4 installed on both computers. I selected the class path the same as was required with OOO 3.3. Would that be causing problems? I don't have a problem accessing the DB on the host computer.

Thanks again!

[DACM]

I currently have the DB files stored at the root level on the server computer, which is likely causing the problem...do I just edit the properties of the folder?

Yes, that will cause problems. Edit the Properties and use the Sharing tab and then verify the changes on the Security tab. You'll need to grant Read and Write access to all clients (perhaps share with 'Everyone' while troubleshooting). Or just move the database to a \user\public\ folder. Public folders should already allow read/write access for 'Everyone.'

I also ran the old installer with the AOO 3.4 installed on both computers. I selected the class path the same as was required with OOO 3.3. Would that be causing problems? I don't have a problem accessing the DB on the host computer.

Well, Class Path selection was not required with OOo 3.3 when using the OOo_hsqldb2.exe installer because the .ini file took care of the Class Path without manual intervention. If you're selecting the Class Path manually in AOO then you're simply overriding that aspect of the installer. The installer's .ini file is not currently setup for LO 3.5+. I guess I'll need to publish a dedicated installer for LO 3.5+.

But either way, the manual Class Path setup is just as easy for many users. Just make sure you're shutting down AOO/LO and the Quickstarter in the taskbar tray when making manual Class Path changes. Also, make sure you're selecting the correct copy of hsqldb.jar because the installer leaves the original intact (for optional use through Class Path selection/override). The installer places HSQLDB 2.2.x (including the associated hsqldb.jar) in a dedicated folder (/Basis/program/classes/hsqldb2) within your AOO installation. I guess you're aware of that already...if you've setup the Class Path manually for HSQLDB 2.2.x after using the Windows installer.