Using OE 11. 4 and Win 8.1, I am trying to connect via shared-memory to a database server started with proserve via AppServer. Unfortunately, the AppServer will not start and it insists that no database server is running although it is.
A client-server connection via the AppServer works ok.
I can also connect without error via shared-memory to this same database via the Procedure Editor.
I've never had this issues on Win7 or Windows server. Is this a Windows 8.1 thing? Am I losing my mind?
Roundtable Product Architect
Is it possible to share the startup parameters of the appserver ?
and the log files ?
this sounds not unknown to me. And that since many releases back. So I doubt this was a recent change.
My understanding is, that when the DB is started from proenv, it’s started under your natural user account and the AppServer processes typically running under LocalSystem don’t have access rights to the shared memory.
Either start the DB using the Admin Service as well, so that it’s running under LocalSystem as well or start the AppServer under a natural user account (the KBase tells you how).
Architect of the SmartComponent Library and WinKit
Are just getting the 1423 error and no other errors before that? Nothing interesting in the appserver logs?
Just the 1423 error. It errors out right away. Usually the appserver churns for bit before it complains but it comes back right away as soon as I try to start it.
Hmmm... everything is started as the same user and you are using the full path to the db with no drive aliases?
Can't really think of anything else besides a typo or special character somewhere that could cause that.
Pretty much everything else should be throwing different errors first (32 bit vs 64 bit, permissions, etc).
Yep.. same user, same machine.. all local. It's the darndest thing. I'll knock on the tech support door and see if they have any insight. The same configuration works fine on Win7 and Windows server.
Have you tried this connection by the AppServer to any other database in shared memory?
How deeply nested in the file directory structure is the database?
If you haven't tested a connection to another DB in shared memory then test that first, and if that works then put that database in the same directory as the failing db and see if it starts failing.
Maybe the issue isn't the db but the directory or the depth of the file path.
PROGRESS SOFTWARE CORPORATION14 Oak Park Drive | Bedford, MA 01730 | USAPHONE +1 781 280-3008 email@example.com
Hmm.. I replied to this a couple of times via email but it didn't make it through.
The AppServer cannot connect to the sports database via shared memory either.
The directory structure is only two levels deep. It works ok with Win7 and WinServer 2008.
For those who may be interested, PSC tech support were able to reproduce my issue. I'll update this thread with the end result in case it may be useful for others.
For those interested, PSC tech support tells me that this is logged as a low priority bug. The work-around is to start the AdminServer manually from the command line.
Low priority? That sounds like a bad choice unless there a lot of DB corruption/shutdown bugs that I am not aware of...
I agree. It only seems to be an issue on Windows 8.1 though so maybe that is why.