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!

Web Forums - SalesLogix Web Client (Pre-7.2)
Forum to discuss using & developing the legacy SalesLogix Web Client (For versions 7.0 and earlier). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Web Client (Pre-7.2) | New Thread

View: Search:

Author Thread: Event Log Write fails!

Snow Monkey
Posts: 214

Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Jul 06 5:38 PM

is there a reason why i cannot write to servers event log from an action in slxweb 6.2.4?

Or is it resolved in some coming fixpacks?

[Reply][Quote]

Jeff Ballard
Posts: 326

Re: Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Jul 06 6:55 PM

Nandu,

There is a reason - they broke the "print" statement in 6.2.3. Don't know if there's a defect # assigned or not. The workaround is do a "senderror" statement *without* an "exit sub" and it'll write whatever you put after it (as the print statement did) but not stop the action execution. Basically, without the exit sub, it functions as the print statement.

Like so:


senderror "Error: " & LogixErrorText


Jeff

[Reply][Quote]

Snow Monkey
Posts: 214

Re: Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 8:15 AM

Thanks it worked!! but...

Dont we have to stop an action completely or else some memory utilization wud build up in the backend ?

Also if this call is going to make the control never come back to the calling routine, what is the point of me writing to the event log(of course! i want to take some other action if some conditions fail).

Now is there an Application_OnError event somewhere in saleslogix so that i can take care of that some other way?

[Reply][Quote]

Jeff Ballard
Posts: 326

Re: Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 10:33 AM

Quote:

Dont we have to stop an action completely or else some memory utilization wud build up in the backend ?

Not necessarily...I usually want the action to continue after writing a variable value (for debugging) so I can see what actually happens. Unless I'm putting in the senderror as a part of error handling, I usually don't exit sub.

Quote:

Also if this call is going to make the control never come back to the calling routine,

It only makes control not come back if you do the Exit Sub. Now, if you have a Sub Main that calls something called "Sub Test" and put a senderror in "Sub Test", I'm not sure if it sends control back to Sub Main as soon as it hits the senderror or not. Usually, After I check for an error, I close open handles, clean up any other items and then do the senderror and an exit sub, sending the standard slx web "We apologize for the inconvenience..." page.

Quote:

Now is there an Application_OnError event somewhere in saleslogix so that i can take care of that some other way?

Nope....Error handling in SLX (web in particular) has always been pretty ugly.

Jeff

[Reply][Quote]

Tim Montgomery
Posts: 23

Re: Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 14 Jul 06 12:28 PM

Defect 1-43713 exists for this issue - marked as fixed in 7.0
Tim

[Reply][Quote]

Snow Monkey
Posts: 214

Re: Event Log Write fails! Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 17 Jul 06 12:30 PM

So they expect ppl like me to upgrade to V7 just for bug fixes like these(everything else seems to be *OK* for me)???
hehe

Thanks Tim

[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 © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 2/19/2025 4:33:27 PM