Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread cannot start database server on a Windows Server 2003 R2
Tue, Apr 18 2006 8:30 AMPermanent Link

"Andre"
Hi,

I am using version Dbisam c/s 4.15

I cannot start the database server on Windows Server 2003 R2 system.
I get an ntdll.dll error. See attachments.

Please advice.
I cannot reproduce the problem on our windows server 2003 R1 system.

Brdgs
Andre

Tue, Apr 18 2006 8:31 AMPermanent Link

"Andre"
forgot the attachment
brdgs
andre


"Andre" <andre@cds-nl..NOSPAM.com> schreef in bericht
news:F9240DB4-73A5-4F88-85F1-452F63D8177C@news.elevatesoft.com...
> Hi,
>
> I am using version Dbisam c/s 4.15
>
> I cannot start the database server on Windows Server 2003 R2 system.
> I get an ntdll.dll error. See attachments.
>
> Please advice.
> I cannot reproduce the problem on our windows server 2003 R1 system.
>
> Brdgs
> Andre
>
>





Attachments: error.doc
Tue, Apr 18 2006 10:04 AMPermanent Link

"Scott Martin"
Are you using an AMD processor?
I exhibited the same exact thing and we had to switch to Intel, problem solved.

Regards,
Scott.

"Andre" <andre@cds-nl..NOSPAM.com> wrote in message news:F9240DB4-73A5-4F88-85F1-452F63D8177C@news.elevatesoft.com...
> Hi,
>
> I am using version Dbisam c/s 4.15
>
> I cannot start the database server on Windows Server 2003 R2 system.
> I get an ntdll.dll error. See attachments.
>
> Please advice.
> I cannot reproduce the problem on our windows server 2003 R1 system.
>
> Brdgs
> Andre
>

Tue, Apr 18 2006 10:57 AMPermanent Link

"Andre"
Thanks scott.
I am not sure I will ask them. It is not my server.

Andre
"Scott Martin" <scottmartin@pdq.net> schreef in bericht
news:FF17C377-1A24-4481-91BF-CC8A9DEE8D08@news.elevatesoft.com...
> Are you using an AMD processor?
> I exhibited the same exact thing and we had to switch to Intel, problem
> solved.
>
> Regards,
> Scott.
>
> "Andre" <andre@cds-nl..NOSPAM.com> wrote in message
> news:F9240DB4-73A5-4F88-85F1-452F63D8177C@news.elevatesoft.com...
>> Hi,
>>
>> I am using version Dbisam c/s 4.15
>>
>> I cannot start the database server on Windows Server 2003 R2 system.
>> I get an ntdll.dll error. See attachments.
>>
>> Please advice.
>> I cannot reproduce the problem on our windows server 2003 R1 system.
>>
>> Brdgs
>> Andre
>>
>
>

Tue, Apr 18 2006 11:46 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Andre,

<< I am using version Dbisam c/s 4.15

I cannot start the database server on Windows Server 2003 R2 system. I get
an ntdll.dll error. See attachments.

Please advice.
I cannot reproduce the problem on our windows server 2003 R1 system. >>

You should update to the latest version and build.  The problem was fixed in
4.20:

http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 18 2006 5:46 PMPermanent Link

"Walter Matte"
I had problems just installing D7 Ent on W2K3.

The solution is to Enable - Data Execution Prevention for Delphi.

On Windows 2003 under:
     My Computer - Properties - Advanced - Performance Settings - Data
Execution Prevention


FYI - This may happen to your applications, developed with Delphi, because
the source of the problem is in sysutils.pas.  I saw the technote in from
Elevatesoft that kept me seeking an answer.  MadExcept had pointed to
TLanguage.Create as the source of the problem.

www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041

The problem turned out to be due to the Data Execution Protection in certain
newer processors preventing the execution of code from the stack, which is
what Delphi is doing in the SysUtils.pas unit with the global Languages
variable. DBISAM was referencing this variable, hence the problem.

So you could try (its very easy) to add DBISAM Server to the Data Execution
Prevention list.  See if that does it.

I posted this a while ago to Borland.General NG and had replies that some
others couldn't get D2006 working with out DEP as well.

Walter

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:6A31913E-1A23-4ECF-BF1B-26509233F73C@news.elevatesoft.com...
> Andre,
>
> << I am using version Dbisam c/s 4.15
>
> I cannot start the database server on Windows Server 2003 R2 system. I get
> an ntdll.dll error. See attachments.
>
> Please advice.
> I cannot reproduce the problem on our windows server 2003 R1 system. >>
>
> You should update to the latest version and build.  The problem was fixed
> in 4.20:
>
> http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Wed, Apr 19 2006 7:35 AMPermanent Link

"Andre"
hi walter
great, it seems to be working.

Thanks a lot.
Andre



"Walter Matte" <walter_@_interlog.com> schreef in bericht
news:B3BCB3B7-F9EA-4256-9535-880EC2EB146D@news.elevatesoft.com...
>I had problems just installing D7 Ent on W2K3.
>
> The solution is to Enable - Data Execution Prevention for Delphi.
>
> On Windows 2003 under:
>      My Computer - Properties - Advanced - Performance Settings - Data
> Execution Prevention
>
>
> FYI - This may happen to your applications, developed with Delphi, because
> the source of the problem is in sysutils.pas.  I saw the technote in from
> Elevatesoft that kept me seeking an answer.  MadExcept had pointed to
> TLanguage.Create as the source of the problem.
>
> www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>
> The problem turned out to be due to the Data Execution Protection in
> certain
> newer processors preventing the execution of code from the stack, which is
> what Delphi is doing in the SysUtils.pas unit with the global Languages
> variable. DBISAM was referencing this variable, hence the problem.
>
> So you could try (its very easy) to add DBISAM Server to the Data
> Execution Prevention list.  See if that does it.
>
> I posted this a while ago to Borland.General NG and had replies that some
> others couldn't get D2006 working with out DEP as well.
>
> Walter
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> news:6A31913E-1A23-4ECF-BF1B-26509233F73C@news.elevatesoft.com...
>> Andre,
>>
>> << I am using version Dbisam c/s 4.15
>>
>> I cannot start the database server on Windows Server 2003 R2 system. I
>> get an ntdll.dll error. See attachments.
>>
>> Please advice.
>> I cannot reproduce the problem on our windows server 2003 R1 system. >>
>>
>> You should update to the latest version and build.  The problem was fixed
>> in 4.20:
>>
>> http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>>
>> --
>> Tim Young
>> Elevate Software
>> www.elevatesoft.com
>>
>>
>
>

Fri, Apr 21 2006 6:14 PMPermanent Link

"Lance R."
Walter,

thank you for posting this.  I had run into some issues with some of my
products not launching. This usually was after SP1 of 2003 was installed.

This fixed it.

Lance

Walter Matte wrote:
> I had problems just installing D7 Ent on W2K3.
>
> The solution is to Enable - Data Execution Prevention for Delphi.
>
> On Windows 2003 under:
>       My Computer - Properties - Advanced - Performance Settings - Data
> Execution Prevention
>
>
> FYI - This may happen to your applications, developed with Delphi, because
> the source of the problem is in sysutils.pas.  I saw the technote in from
> Elevatesoft that kept me seeking an answer.  MadExcept had pointed to
> TLanguage.Create as the source of the problem.
>
> www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>
> The problem turned out to be due to the Data Execution Protection in certain
> newer processors preventing the execution of code from the stack, which is
> what Delphi is doing in the SysUtils.pas unit with the global Languages
> variable. DBISAM was referencing this variable, hence the problem.
>
> So you could try (its very easy) to add DBISAM Server to the Data Execution
> Prevention list.  See if that does it.
>
> I posted this a while ago to Borland.General NG and had replies that some
> others couldn't get D2006 working with out DEP as well.
>
> Walter
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> news:6A31913E-1A23-4ECF-BF1B-26509233F73C@news.elevatesoft.com...
>> Andre,
>>
>> << I am using version Dbisam c/s 4.15
>>
>> I cannot start the database server on Windows Server 2003 R2 system. I get
>> an ntdll.dll error. See attachments.
>>
>> Please advice.
>> I cannot reproduce the problem on our windows server 2003 R1 system. >>
>>
>> You should update to the latest version and build.  The problem was fixed
>> in 4.20:
>>
>> http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>>
>> --
>> Tim Young
>> Elevate Software
>> www.elevatesoft.com
>>
>>
>
>
>
Sat, Apr 22 2006 7:51 AMPermanent Link

"Walter Matte"
Glad to publish my findings... it was a real pain for me for a few days...

Take a read in the Disscussion Group  "Data Exception Prevention sysutil fix
in DBISAM and other apps." thread , 4/21/2006 Graham Wood.
There is a unit in CodeCentral that you can add to uses before sysutil that
fixes this in our Delphi Apps.

Walter

"Lance R." <lance@lance.ws> wrote in message
news:3A3B5B8A-EAB8-4738-9B61-AE27BCD7D5DB@news.elevatesoft.com...
> Walter,
>
> thank you for posting this.  I had run into some issues with some of my
> products not launching. This usually was after SP1 of 2003 was installed.
>
> This fixed it.
>
> Lance
>
> Walter Matte wrote:
>> I had problems just installing D7 Ent on W2K3.
>>
>> The solution is to Enable - Data Execution Prevention for Delphi.
>>
>> On Windows 2003 under:
>>       My Computer - Properties - Advanced - Performance Settings - Data
>> Execution Prevention
>>
>>
>> FYI - This may happen to your applications, developed with Delphi,
>> because
>> the source of the problem is in sysutils.pas.  I saw the technote in from
>> Elevatesoft that kept me seeking an answer.  MadExcept had pointed to
>> TLanguage.Create as the source of the problem.
>>
>> www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>>
>> The problem turned out to be due to the Data Execution Protection in
>> certain
>> newer processors preventing the execution of code from the stack, which
>> is
>> what Delphi is doing in the SysUtils.pas unit with the global Languages
>> variable. DBISAM was referencing this variable, hence the problem.
>>
>> So you could try (its very easy) to add DBISAM Server to the Data
>> Execution Prevention list.  See if that does it.
>>
>> I posted this a while ago to Borland.General NG and had replies that some
>> others couldn't get D2006 working with out DEP as well.
>>
>> Walter
>>
>> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in
>> message news:6A31913E-1A23-4ECF-BF1B-26509233F73C@news.elevatesoft.com...
>>> Andre,
>>>
>>> << I am using version Dbisam c/s 4.15
>>>
>>> I cannot start the database server on Windows Server 2003 R2 system. I
>>> get an ntdll.dll error. See attachments.
>>>
>>> Please advice.
>>> I cannot reproduce the problem on our windows server 2003 R1 system. >>
>>>
>>> You should update to the latest version and build.  The problem was
>>> fixed in 4.20:
>>>
>>> http://www.elevatesoft.com/scripts/incident.dll?action=viewrep&release=4.19&type=f&incident=2041
>>>
>>> --
>>> Tim Young
>>> Elevate Software
>>> www.elevatesoft.com
>>>
>>>
>>
>>
>>
>

Sun, Apr 23 2006 11:21 PMPermanent Link

Lance R
Great catch. Thanks again!

Lance

Walter Matte wrote:
> Glad to publish my findings... it was a real pain for me for a few days...
>
> Take a read in the Disscussion Group  "Data Exception Prevention sysutil fix
> in DBISAM and other apps." thread , 4/21/2006 Graham Wood.
> There is a unit in CodeCentral that you can add to uses before sysutil that
> fixes this in our Delphi Apps.
>
> Walter
>
Image