![]() | ![]() Products ![]() ![]() ![]() ![]() |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Client/Server » View Thread |
Messages 1 to 7 of 7 total |
![]() |
Wed, Aug 1 2007 7:01 PM | Permanent Link |
"Adam H." | Hi Tim,
Sorry to take so long getting back to you regarding this one... > << 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. I have updated them back to 4.25b5, and inserted the /NI parameter, but we are still experiencing access voilation messages. The message seems to always have the same address, and the message is: 8/2/2007 8:23:10 AM [ERROR] Engine error [Access violation at address 0047E7EA in module 'dbsrvr.exe'. Write of address 00000233] [Client Version: 4.25 User Name: jo Address: 10.30.11.126 Encrypted: No Request: REQUEST_FREESTMT Thread: 1916 Session: 40884232] The dbisam server is stock standard (no recompilation, etc) of 4.25b5 running on MS Windows Server 2003 R2 Std Edition SP2 with 2 CPU's and 2GB Ram. Effectively apart from the DBISam server, this server is a printer and file server. Best Regards Adam. |
Thu, Aug 2 2007 1:19 PM | Permanent Link |
Jason Lee | Adam,
I had the same issue a while back (search for REQUEST_FREESTMT in newsgroups) with no resolution. Are you using threads? ~Jason Lee Adam H. wrote: |
Thu, Aug 2 2007 7:35 PM | Permanent Link |
"Adam H." | Hi Jason,
> I had the same issue a while back (search for REQUEST_FREESTMT in > newsgroups) with no resolution. Are you using threads? There are one or two users on the systems that have a serial port component running which is using threads, but the Access Voilations I'm receiving are happening on both these users, and also users that don't have the comport active. (Unless those users running the Serial component thread can cause the server to crash on 'others'). Sorry for the vague answer, but I'm not really up to scratch with threads. I only know that the ComPort component I'm using (the TApdComPort from Turbopower I believe) uses threads to monitor the serial port activity. Best Regards Adam. |
Fri, Aug 3 2007 1:10 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Adam,
<< The message seems to always have the same address, and the message is: 8/2/2007 8:23:10 AM [ERROR] Engine error [Access violation at address 0047E7EA in module 'dbsrvr.exe'. Write of address 00000233] [Client Version: 4.25 User Name: jo Address: 10.30.11.126 Encrypted: No Request: REQUEST_FREESTMT Thread: 1916 Session: 40884232] >> We see that one the most with regard to these types of reports, but have, as of yet, been unable to come up with a reproducible scenario. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Aug 6 2007 2:54 AM | Permanent Link |
"Adam H." | Hi Tim,
Thanks for your reply... > We see that one the most with regard to these types of reports, but have, > as of yet, been unable to come up with a reproducible scenario. I thought about recompiling the engine with Eurekalog to get a trap when the exception occurs (line no, call stacks, etc) - but when I compile the server with eurekalog and try and run - it just closes on me. Do you know what might be causing this? Thanks & Regards Adam. |
Mon, Aug 6 2007 4:14 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. ![]() | Adam,
<< Do you know what might be causing this? >> You might need to register the dbisammm memory manager with EurekaLog. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Aug 6 2007 7:09 PM | Permanent Link |
"Adam H." | Hi Tim,
> << Do you know what might be causing this? >> > > You might need to register the dbisammm memory manager with EurekaLog. Thanks for that. I'll look into this and see what I can find. Cheers Adam. |
This web page was last updated on Wednesday, August 14, 2024 at 07:31 PM | Privacy Policy![]() © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? ![]() |