Icon View Thread

The following is the text of the current message along with any replies.
Messages 11 to 19 of 19 total
Thread Engine Error # 11010
Mon, Apr 7 2008 5:55 PMPermanent Link

"Jerry Clancy"
More input. I blew away the two TDBISAMDatabase components and all
references to them, made sure DatabaseName was set in all tables, and same
result: 11010.

Jerry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:A534552C-5B02-4C92-87D9-615491DE17FC@news.elevatesoft.com...
> Jerry,
>
> << Thanks, Tim. We'll give it a try. The local host application in Run |
> Parameters | Local is set to the full path of the server .exe on the local
> system. It was one of the first things I checked. >>
>
> Actually, I meant using a full path in the TDBISAMDatabase.Directory
> property or the TDBISAMTable.DatabaseName property, not the host
> application directory.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tue, Apr 8 2008 1:42 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jerry,

<< Oh, I did that a long time ago. Still doesn't work with a valid local
directory in both (the only) TDBISAMDatabase components. >>

If you want to send me the project, I can test it here and see what I can
find.  It should only take a few minutes to get you a response.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 8 2008 3:18 PMPermanent Link

"Jerry Clancy"
Tim,

Glad to hear from you because I'm out of options. Appreciate the offer,
however, the project is a monster with some 50 units and uses even more
databases with gigabytes of data. Taxes have been awaiting attention for
three days but I'll have to spend some time thinking about how to attack
this.

The answer lies is solving the riddle of why it won't work with the debugger
in the IDE but will run if I manually start the very same server and run the
same compiled localhost isapi dll. This seems to tell me that there is
something screwy about the IDE setup for this app (but only this app) but I
can't find anything. Since I stripped the app of the DBISAMDatabase
components, I haven't a clue why I'm getting the same message re dbisam.lck.
Is there something I don't know about that file?

Is it possible (on this new XP Pro system) that there is some security issue
with the spawned (by the IDE) server process that doesn't apply if started
manually?

Thoughts from any and all welcome.

Jerry




"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:02F64036-8B89-4ECC-B7BD-4FD6B16C76EA@news.elevatesoft.com...
> Jerry,
>
> << Oh, I did that a long time ago. Still doesn't work with a valid local
> directory in both (the only) TDBISAMDatabase components. >>
>
> If you want to send me the project, I can test it here and see what I can
> find.  It should only take a few minutes to get you a response.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tue, Apr 8 2008 4:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jerry,

<< The answer lies is solving the riddle of why it won't work with the
debugger in the IDE but will run if I manually start the very same server
and run the same compiled localhost isapi dll. This seems to tell me that
there is something screwy about the IDE setup for this app (but only this
app) but I can't find anything. Since I stripped the app of the
DBISAMDatabase components, I haven't a clue why I'm getting the same message
re dbisam.lck. Is there something I don't know about that file? >>

No, you've still got a DBISAM reference in there someplace, otherwise you
wouldn't be getting a DBISAM error.  As for these issues, it is quite normal
with relative path issues to have the app work in some cases and not others,
with the defining difference being the current working directory in each
execution instance.

<< Is it possible (on this new XP Pro system) that there is some security
issue with the spawned (by the IDE) server process that doesn't apply if
started manually? >>

Well, with D5 you have to load the symbols for a DLL manually after setting
up a module load breakpoint in the DLL due to the fact that XP introduced
some debugging security constraints that D5 is not made to handle.
Debugging the project in D7 would be easier, if you have it.  However, you
should still get the error.  The only difference is whether the debugger
points directly to the line where the error occurs, or whether it just pops
up a message dialog.

See here:

http://groups.google.com/group/borland.public.delphi.ide/browse_frm/thread/700248355302e144/87af4dfcd8d49181?lnk=st&q=debug+delphi+5+DLLs+windows+xp#87af4dfcd8d49181

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Apr 8 2008 4:50 PMPermanent Link

"Jerry Clancy"
Don't have D7. Looked at the reference but what strikes me as odd is that
this doesn't seem to happen to other apps on this system but, then I haven't
rebuilt them either.

It doesn pop up an error message. You just can't find where it is in the
code.

Will check out what the google groups have to say.

Thanks,

Jerry

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:3F6A1ECE-9F73-4F0E-9138-721C8F80D672@news.elevatesoft.com...
> Jerry,
>
> << The answer lies is solving the riddle of why it won't work with the
> debugger in the IDE but will run if I manually start the very same server
> and run the same compiled localhost isapi dll. This seems to tell me that
> there is something screwy about the IDE setup for this app (but only this
> app) but I can't find anything. Since I stripped the app of the
> DBISAMDatabase components, I haven't a clue why I'm getting the same
> message re dbisam.lck. Is there something I don't know about that file? >>
>
> No, you've still got a DBISAM reference in there someplace, otherwise you
> wouldn't be getting a DBISAM error.  As for these issues, it is quite
> normal with relative path issues to have the app work in some cases and
> not others, with the defining difference being the current working
> directory in each execution instance.
>
> << Is it possible (on this new XP Pro system) that there is some security
> issue with the spawned (by the IDE) server process that doesn't apply if
> started manually? >>
>
> Well, with D5 you have to load the symbols for a DLL manually after
> setting up a module load breakpoint in the DLL due to the fact that XP
> introduced some debugging security constraints that D5 is not made to
> handle. Debugging the project in D7 would be easier, if you have it.
> However, you should still get the error.  The only difference is whether
> the debugger points directly to the line where the error occurs, or
> whether it just pops up a message dialog.
>
> See here:
>
> http://groups.google.com/group/borland.public.delphi.ide/browse_frm/thread/700248355302e144/87af4dfcd8d49181?lnk=st&q=debug+delphi+5+DLLs+windows+xp#87af4dfcd8d49181
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Tue, Apr 8 2008 5:02 PMPermanent Link

"Jerry Clancy"
Tim,

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:3F6A1ECE-9F73-4F0E-9138-721C8F80D672@news.elevatesoft.com...
> Jerry,
>
> No, you've still got a DBISAM reference in there someplace, otherwise you
> wouldn't be getting a DBISAM error.  As for these issues, it is quite
> normal with relative path issues to have the app work in some cases and
> not others, with the defining difference being the current working
> directory in each execution instance.

Would you expound a bit on "current working directory". What would it be in
this context and is it related to dbisam and/or dbisam.lck?


> Well, with D5 you have to load the symbols for a DLL manually after
> setting up a module load breakpoint in the DLL due to the fact that XP
> introduced some debugging security constraints that D5 is not made to
> handle.

How do you lload these manually? I have the IDE setup to include all
symbols, including those of the IDE.

Jerry

Tue, Apr 8 2008 5:10 PMPermanent Link

"Jerry Clancy"
Ignore the question below in the previous post. I just realized that this is
the Directory property in the two TDBISAMDatabase component which I blew
away. However, even when I had them I set the the property to the correct
fully-qualified path, Connected = False and all the table DatabaseNames to
the component name, it still gave me the error.

Jerry

"Jerry Clancy" <jclancy@billtrak.com> wrote in message
news:42F2336E-058D-4B11-8448-F44F64ED8C36@news.elevatesoft.com...
> Tim,
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
> news:3F6A1ECE-9F73-4F0E-9138-721C8F80D672@news.elevatesoft.com...
>> Jerry,
>>
> Would you expound a bit on "current working directory". What would it be
> in this context and is it related to dbisam and/or dbisam.lck?

Tue, Apr 8 2008 9:14 PMPermanent Link

"Jerry Clancy"
Tim,

Found the problem. Since breakpoints don't seem to be working (symbols
apparently not loaded in XP, etc.), on a hunch I checked where I am setting
the path variable that is used to open most tables. This occurs almost
immediately in the ServerController function (IW). A function I was using
successfully for years --
ExtractFilePath(GetModuleFileNameStr), which uses GetModuleFileName --  
seemed to be returning in XP the a path relative to the root of the server
instead of the fully-qualified one it had in Win2K. In our other apps we
used a different function which works in all versions of Windows.

The lack of functioning breakpoints is what caused the delay in identifying
the cause. I had one there but no halt occurred in XP.

I can't tell you how relieved I am to find this and I want to thank you for
your comments and suggestions.

Now on to taxes.

Jerry

Wed, Apr 9 2008 11:26 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Jerry,

<< The lack of functioning breakpoints is what caused the delay in
identifying the cause. I had one there but no halt occurred in XP. >>

Yep, it's a real PIA, especially once you realize that the breakpoints
aren't "active".

<< I can't tell you how relieved I am to find this and I want to thank you
for your comments and suggestions.

Now on to taxes. >>

There goes that feeling of relief..... Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Previous PagePage 2 of 2
Jump to Page:  1 2
Image