On 10/4/2012 3:37 PM, Aage Johansen wrote:
> However, srvadmin refuses to work.  Last time I tried to start it there
> was a pause (for some longish seconds), and an error message ("216", IIRC).

The admin port is different from regular data access port (dbsrvr
default port for data is is 12005 and admin 12006) so make sure your
firewall allows access.

I don't know about error 216 and only search result i found that might
apply is the that data execution prevention so if related then make sure
it's not enabled in windows for all apps.

Raul

On 04.10.2012 23:26, Raul wrote:
> On 10/4/2012 3:37 PM, Aage Johansen wrote:
>> However, srvadmin refuses to work.  Last time I tried to start it there
>> was a pause (for some longish seconds), and an error message ("216",
>> IIRC).
>
> The admin port is different from regular data access port (dbsrvr
> default port for data is is 12005 and admin 12006) so make sure your
> firewall allows access.
>
> I don't know about error 216 and only search result i found that might
> apply is the that data execution prevention so if related then make sure
> it's not enabled in windows for all apps.
>
> Raul
>

I don't think we did anything particular for 12005 (or 12006), and
wouldn't a blocked port raise another type of error?  We did scratch our
heads for some time trying to figure out how to configure the
(Windows/2008) firewall - maybe not a big success.
We tried srvadmin locally - is there some log file that it tries
(unsuccessfully) to create, perhaps?

--
Aage J.

On 10/4/2012 7:12 PM, Aage Johansen wrote:
> wouldn't a blocked port raise another type of error?  We did scratch our

Yes it would hence i suggested checking DEP settings as that's the only
time i've seen OS error 216.

> We tried srvadmin locally - is there some log file that it tries
> (unsuccessfully) to create, perhaps?

I think there is a trace under svradmin options that might help.

However i would suggest you double-check your settings and get the exact
errors:
- confirm dbsrvr is running on 12005 and 12006 for admin port
- confirm you can access the port normally (e.g. use telnet localhost 12006)
- try the srvadmin both locally and remotely and get the exact error.

Raul

Aage,

<< Any clues about the "216"? >>

If you could get the complete error message, it would help.  I suspect that
you're seeing a runtime error 216, which usually occurs when there's a fatal
error during startup in a Delphi application.

Tim Young
Elevate Software
www.elevatesoft.com

On 09.10.2012 21:47, Tim Young [Elevate Software] wrote:
> Aage,
>
> << Any clues about the "216"? >>
>
> If you could get the complete error message, it would help.  I suspect
> that you're seeing a runtime error 216, which usually occurs when
> there's a fatal error during startup in a Delphi application.
>
> Tim Young
> Elevate Software
> www.elevatesoft.com


Starting srvadmin.exe results in
Runtime error 216 at 0003134

Starting dbsys.exe results in
Runtime error 216 at 000031AC


Thanks for looking into this.  The workaround is to do administration
via Remote Desktop.  This works very well according to the user/customer.
Looking at the version info (on the set of files that I copied to my
machine) it says 4.19.1.1 for both.  I believe this is the actual
versions used.

--
Aage J.

Aage,

<< Starting srvadmin.exe results in
Runtime error 216 at 0003134

Starting dbsys.exe results in
Runtime error 216 at 000031AC >>

You're probably seeing something related to this:

http://www.elevatesoft.com/incident?action=viewrep&category=dbisam&release=4.19&incident=2041

Especially since it's happening in any DBISAM application, not just the
server.  I would definitely update to 4.20 or higher (preferably 4.27), and
see if that fixes the issue.

Tim Young
Elevate Software
www.elevatesoft.com