Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread DBISAM V3.3 Server Engine and Microsoft SBS 2008 Issue
Wed, Jun 24 2009 9:30 PMPermanent Link

"Al Vas"
Hi,

We have a client who has just installed SBS 2008.  We have a weird problem
in that when we run Dbsrvr.exe as a service, when our application from a
client PC tries to access it, we get an error '#11276....connection to the
database at xxx.xxx.xxx.xxx has been lost'.  Running the application from
the server to access it runs fine.  Running dbsrvr.exe as an application
(rather than a service) and then accessing the application from a client
runs fine (although only once we opened ports 12005 and 12006).  Running in
non-client server mode ie reading tables directly also works fine.

Seems to me there's some sort of rights issue on the service login, any
ideas?

Also their IT (who have been trying to help resolve) claims that SBS 2008
and standard server 2008 are completely different beasts and the fact that
DBISAM engine runs on a standard server 2008 doesnt mean its compatible to
work with SBS 2008.  Would this be correct?  Sounds like rubbish to me.

Finally, if we aren't successful with solving this (aassuming DBISAM V3.30
is compatible with SBS 2008), is there anyone who, for a fee, would be able
to remotely connect and try and help resolve this iusse as it is critical
for this employee?  They are Australian-based lthough this probably doesnt
matter for remote access.

All help appreciated.

Thanks

Alex

Wed, Jun 24 2009 10:30 PMPermanent Link

"Raul"
No experience with SBS2008 but few suggestions.

It actually sounds like non user-mode issue. Windows 2008 (and Vista)
introduced the session 0 isolation mode which might be affecting you since
services run there. Options are limited to resolve this.

Still couple of questions:

- What account are you running the dbsrvr.exe under when running as a
service ? I suggest creating a dedicated account with adequate permissions
(make it admin for now) and not using built-in ones like local service
account.

- Have you tried marking the dbsrvr.exe as WinXP compatible for example
(right-click on exe and look for compatibility tab) to see if it helps. This
should in theory help around the session 0 issue.

Raul




"Al Vas" <noreply@noreply.com> wrote in message
news:4E706015-85CF-46AA-8DC7-41A9D76AA687@news.elevatesoft.com...
> Hi,
>
> We have a client who has just installed SBS 2008.  We have a weird problem
> in that when we run Dbsrvr.exe as a service, when our application from a
> client PC tries to access it, we get an error '#11276....connection to the
> database at xxx.xxx.xxx.xxx has been lost'.  Running the application from
> the server to access it runs fine.  Running dbsrvr.exe as an application
> (rather than a service) and then accessing the application from a client
> runs fine (although only once we opened ports 12005 and 12006).  Running
> in non-client server mode ie reading tables directly also works fine.
>
> Seems to me there's some sort of rights issue on the service login, any
> ideas?
>
> Also their IT (who have been trying to help resolve) claims that SBS 2008
> and standard server 2008 are completely different beasts and the fact that
> DBISAM engine runs on a standard server 2008 doesnt mean its compatible to
> work with SBS 2008.  Would this be correct?  Sounds like rubbish to me.
>
> Finally, if we aren't successful with solving this (aassuming DBISAM V3.30
> is compatible with SBS 2008), is there anyone who, for a fee, would be
> able to remotely connect and try and help resolve this iusse as it is
> critical for this employee?  They are Australian-based lthough this
> probably doesnt matter for remote access.
>
> All help appreciated.
>
> Thanks
>
> Alex
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4186 (20090624) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>



__________ Information from ESET NOD32 Antivirus, version of virus signature database 4186 (20090624) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



Thu, Jun 25 2009 12:41 AMPermanent Link

"Al Vas"
Hi Raul,

Thanks for your response.  Seemded to have solved it in the end.  We in the
past normally installed the databae engine in the application folder.  This
is usually on another drive.  It appears that maybe the service login didnt
have rights to that folder where dbsrvr sits or something of that nature,
because once I moved it to the c:\program files (x86)' folder the service
allowed access fine.

Thanks again

Alex

"Raul" <raul@raul.ca> wrote in message
news:06D4853C-3ADB-4040-93A3-571056E0C25C@news.elevatesoft.com...
> No experience with SBS2008 but few suggestions.
>
> It actually sounds like non user-mode issue. Windows 2008 (and Vista)
> introduced the session 0 isolation mode which might be affecting you since
> services run there. Options are limited to resolve this.
>
> Still couple of questions:
>
> - What account are you running the dbsrvr.exe under when running as a
> service ? I suggest creating a dedicated account with adequate permissions
> (make it admin for now) and not using built-in ones like local service
> account.
>
> - Have you tried marking the dbsrvr.exe as WinXP compatible for example
> (right-click on exe and look for compatibility tab) to see if it helps.
> This should in theory help around the session 0 issue.
>
> Raul
>
>
>
>
> "Al Vas" <noreply@noreply.com> wrote in message
> news:4E706015-85CF-46AA-8DC7-41A9D76AA687@news.elevatesoft.com...
>> Hi,
>>
>> We have a client who has just installed SBS 2008.  We have a weird
>> problem in that when we run Dbsrvr.exe as a service, when our application
>> from a client PC tries to access it, we get an error
>> '#11276....connection to the database at xxx.xxx.xxx.xxx has been lost'.
>> Running the application from the server to access it runs fine.  Running
>> dbsrvr.exe as an application (rather than a service) and then accessing
>> the application from a client runs fine (although only once we opened
>> ports 12005 and 12006).  Running in non-client server mode ie reading
>> tables directly also works fine.
>>
>> Seems to me there's some sort of rights issue on the service login, any
>> ideas?
>>
>> Also their IT (who have been trying to help resolve) claims that SBS 2008
>> and standard server 2008 are completely different beasts and the fact
>> that DBISAM engine runs on a standard server 2008 doesnt mean its
>> compatible to work with SBS 2008.  Would this be correct?  Sounds like
>> rubbish to me.
>>
>> Finally, if we aren't successful with solving this (aassuming DBISAM
>> V3.30 is compatible with SBS 2008), is there anyone who, for a fee, would
>> be able to remotely connect and try and help resolve this iusse as it is
>> critical for this employee?  They are Australian-based lthough this
>> probably doesnt matter for remote access.
>>
>> All help appreciated.
>>
>> Thanks
>>
>> Alex
>>
>>
>>
>> __________ Information from ESET NOD32 Antivirus, version of virus
>> signature database 4186 (20090624) __________
>>
>> The message was checked by ESET NOD32 Antivirus.
>>
>> http://www.eset.com
>>
>>
>>
>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 4186 (20090624) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
Thu, Jun 25 2009 10:26 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Alex,

<< We have a client who has just installed SBS 2008.  We have a weird
problem in that when we run Dbsrvr.exe as a service, when our application
from a client PC tries to access it, we get an error '#11276....connection
to the database at xxx.xxx.xxx.xxx has been lost'. >>

In such situations, the DBISAM Database Server log (dbsrvr.log) accessible
from the Server Administration Utility will allow you to see if there are
any errors occurring in the service.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image