Subject | RE: [firebird-support] Service Manager is unavailable on server |
---|---|
Author | Paul Vinkenoog |
Post date | 2004-08-28T14:02:17Z |
Hi Michael,
suppose it detects a Classic Server and concludes "Aha - no Services
manager!"
I'm not saying this is the case, but it might be worthwhile checking
if you can backup/restore with other admin tools. Have you got any?
If not, you could e.g. download an eval version of DB Workbench and
see if that works.
Another cause *might be* a wrong client lib floating around your
Windows system dir, left over from a previous install.
Did you try to connect locally *and* via localhost/127.0.0.1, and do
you get the same message in both cases?
Other than that, I'm afraid I'm clueless...
Greetings,
Paul Vinkenoog
>> I am running superserver.OK, so there must be a Services Manager.
> By the way, I have also,I don't know EMS Interbase/Firebird Manager, but... (just an idea):
> 1 rebooted,
> 2 Reinstalled Firebird
> 3 Reinstalled EMS Interbase/Firebird Manager
> 4 This may be the first time I have tried to restore
> a db since I upgraded to FB 1.5 - I don't remember for sure.
suppose it detects a Classic Server and concludes "Aha - no Services
manager!"
I'm not saying this is the case, but it might be worthwhile checking
if you can backup/restore with other admin tools. Have you got any?
If not, you could e.g. download an eval version of DB Workbench and
see if that works.
Another cause *might be* a wrong client lib floating around your
Windows system dir, left over from a previous install.
Did you try to connect locally *and* via localhost/127.0.0.1, and do
you get the same message in both cases?
Other than that, I'm afraid I'm clueless...
Greetings,
Paul Vinkenoog