Hi Tim,

> << I dropped the server back to 4.24 at the start of the week to see if
> that makes a difference. Since doing it, we have had less problems (but
> not totally eliminated).. >>
>
> I know it's been fashionable among several customers that dropping back to
> prior versions reportedly solves issues, but there's no substance to such
> statements as far as I know.   Whatever is causing these types of errors
> has probably been in there for a long time, the reason being that I simply
> have never been able to reproduce any of it.  If I could reproduce such
> AVs, or if I ever experienced them here in either our use of the database
> server or the automated testing, it would be fixed immediately.

I'm completely aware that you would have this fixed immediately if you could
reproduce the problem, - and I have always appreciated the support that you
give. It is exceptional!

I understand that without being able to reproduce the AV's you're going to
have a tough (if not impossible) task at trying to fix the problem. Please
don't take any of my posts as being impatient or upset. (I couldn't be more
happier with the service you provide!)

I'm just posting my current observations here just incase anything triggers
something that maybe of assistance.

> One other thing - are you running the database server with or without the
> user interface/system tray functionality ?

I believe it's without - but can't be totally sure (unless it's as simple as
looking at the system tray).. I installed the service by typing in
"dbsrvr.exe /install", and can see no icon in the system tray - although in
the services properties the option "Allow service to interact with desktop"
is ticked.

Cheers

Adam.

Adam,

<< I understand that without being able to reproduce the AV's you're going
to have a tough (if not impossible) task at trying to fix the problem.
Please don't take any of my posts as being impatient or upset. (I couldn't
be more happier with the service you provide!) >>

Not at all.  I was just trying to clarify that moving to an older
version may only appear to, or actually correct, an isssue due to chance.
Therefore, it really doesn't fix the issue, but rather simply postpones it.

<< I believe it's without - but can't be totally sure (unless it's as simple
as looking at the system tray).. I installed the service by typing in
"dbsrvr.exe /install", and can see no icon in the system tray - although in
the services properties the option "Allow service to interact with desktop"
is ticked. >>

Check the dbsrvr.ini file in the same directory as the dbsrvr.exe
application and make sure that the No User Interface value is set to 1.
Then also uncheck the Allow service to interact... check box.

Let me know if that helps at all.  We've seen some issues with listviews
under heavy load on 2003 here with our server, so it may be a similar issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

Good Morning Tim,

> Check the dbsrvr.ini file in the same directory as the dbsrvr.exe
> application and make sure that the No User Interface value is set to 1.
> Then also uncheck the Allow service to interact... check box.
>
> Let me know if that helps at all.  We've seen some issues with listviews
> under heavy load on 2003 here with our server, so it may be a similar
> issue.

Thanks for the suggestion, however - this is wierd. I have no dbsrvr.ini
file located in the same directory (nor on the entire machine).  :-/

Cheers

Adam.

Adam,

<< Thanks for the suggestion, however - this is wierd. I have no dbsrvr.ini
file located in the same directory (nor on the entire machine).  :-/ >>

Are you starting up the service with the /NI flag instead ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Good Morning Tim,

> << Thanks for the suggestion, however - this is wierd. I have no
> dbsrvr.ini file located in the same directory (nor on the entire machine).
> :-/ >>
>
> Are you starting up the service with the /NI flag instead ?

There are no startup parameters in the service manager property for DBISam.
If I whack the /NI parameter in there, does that effectively do the same
thing?

Also - should I be concerned that their is no .ini file with the executable?

Cheers

Adam.

Adam,

<< There are no startup parameters in the service manager property for
DBISam. If I whack the /NI parameter in there, does that effectively do the
same thing? >>

Yes, that should work also.

<< Also - should I be concerned that their is no .ini file with the
executable? >>

Not unless you specifically wanted to change some startup parameters via the
..INI file.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> << There are no startup parameters in the service manager property for
> DBISam. If I whack the /NI parameter in there, does that effectively do
> the same thing? >>
>
> Yes, that should work also.

Thanks for that. I'm not going to have access again to their sever for a
number of days, but shall give it a go as soon as I can and report back.

Cheers

Adam.

It's been a while since I looked at this thread so I thought I should report that I've
had not a single error since removing the trigger code from my server.

Tony,

<< It's been a while since I looked at this thread so I thought I should
report that I've had not a single error since removing the trigger code from
my server.  >>

Interesting.  Did you give me the code to your server to look at yet ?

--
Tim Young
Elevate Software
www.elevatesoft.com