Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, April 19, 2024 
 
slxdeveloper.com Community Forums  
   
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
 Administration Forums - Networks & Misc Technical
Forum to discuss networking and miscelleanous technical topics. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to Networks & Misc Technical | New ThreadView:  Search:  
 Author  Thread: SlxLoggingTrigger
Derek
Posts: 115
 
SlxLoggingTriggerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 07 Sep 09 1:57 AM
Hello All.
I've been trying to find out what would be causing the following error (as below) in the event log without much success.

Execute Method. Error @ Line: 4 Table: ACCOUNT TriggerType: 1 Message: Access violation at address 0427F32C in module 'SLXOLEDB.dll'. Read of address 00000000

any information on what the causes and solutions are is greatly appreciated.


[Reply][Quote]
Michael Rogers
Posts: 70
 
Re: SlxLoggingTriggerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Sep 09 2:41 PM
Derek, You may find it interesting to note someone on IT Toolbox asked the same question in July of last year with no response (the SQL sample from the profiler is worth its weight in gold!) I am having the same issue on the opportunity table in v7.2.1 for only one user (so far?) out of 500. Are you seeing this as an isolated event also, or impacting multiple users? My user is getting this when she has an account open and clicks the Navbar button for Opportunities. It crashed SLX on her 4 times today, and 7 over the course of two concurrent days last week. Between those outbreaks, no reported issues.
[Reply][Quote]
Derek
Posts: 115
 
Re: SlxLoggingTriggerYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 10 Sep 09 1:12 AM
Hi Michael,

Thanks for the reply. I did search through IT-ToolBox and really not much on a solution is provided. I agree with what you say about using the SLX Profiler, but in this case it doesn't really help me much as we have 2 terminal servers with Citrix that have the Saleslogix Client and then we have the main application server which contains the Saleslogix server application and administration.

There are well over 100 users (not just within the company network) connecting to Saleslogix, when I run the SLX Profiler on the application server and go through the process no errors are identified.

Thanks anywahy for your suggestions.
[Reply][Quote]
 Page 1 of 1 
  You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

   Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 4/19/2024 5:14:14 PM