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 - General Administration
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to General Administration | New Thread

View: Search:

Author

Thread: 6.1.1 - Basic had an error. Context: leaccount.

Justin Kuehlthau
Posts: 24

6.1.1 - Basic had an error. Context: leaccount. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 27 Oct 06 11:14 AM

Hello,

All users of the 6.1.1 Support Client are getting the following errors seemingly at random. Closing and re-opening makes it go away, but it eventually comes back.

Support
Genera: Error on line: 65 - Unspecified failure

Click OK, Then:

Basic had an error...
Context: leAccount
@0: Basic System:META ByID When Exit
Context: leAccount
@0: Basic Ticket:META Ticket Account Default Assignment
Status: 0xFFFFFFF

The only other similar issue I found was in a post from ITToolbox, but there was no response:
-----------------------------
Errors in Supportlogix adding/editing Tickets
Posted by Michelle Poston on 8/16/2004 5:53:00 PM

Since we implemented Supportlogix 3 years ago, our users have been reporting errors while adding and editing Support Tickets. These errors are random and cannot be duplicated and they happen for most users - even the Sysadmins from time to time. We have called Saleslogix Support about this issue and have researched but still have not come up with an answer. I was hoping that someone out there would have some insight as to why we are receiving these errors. Any help would be appreciated!
The errors are:
Basic had an error. Context: leAccount. @0: Basic System: Meta Self Text to Global. Error line 31 - Unspecified Failure.

Basic had an error. Context: ebTicketID. @0: Basic System: Meta Ticket Account Default Assignment. Error line 65 - Unspecified Failure.

What is strange about these errors is that they are reporting the last line in the scripts. (reported Error line - 1). And I also noticed that they are both using GlobalInfoSet. Could this function be causing a problem?
-----------------------------

Any ideas why this could be happening?

Thank you,
Justin K.

[Reply][Quote]

Sarah Peterson
Posts: 37

Re: 6.1.1 - Basic had an error. Context: leaccount. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 21 Mar 07 9:06 AM

We have been experiencing the same types of errors since we first loaded the support client as well back in 2004. We have spent countless hours in researching this issue and have continued to come up empty handed. A few users just recently noticed that they would get the error at 59 minutes after the hour. I started digging into this issue yet again but have not been able to consistently reproduce the error at any given time, let alone 59 minutes after the hour.

If anybody would be able to offer any assistance that would be great. However, seeing that the post on ITToolbox has been out there for several years without any response and this posting has been listed for quite awhile without any response, I can only assume nobody knows how to address the problem.

If that is the case, then I would just like to mention the frustration of being a customer of a product that has had known issues for over 3 years that have not been addressed in newer releases. It will not score any brownie points here for our company that currently has over 300 employees that have access to the Support client.

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: 6.1.1 - Basic had an error. Context: leaccount. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 22 Mar 07 9:21 AM

I've seen situations where there was an issue w/Hours of operation... In The Admin...
Check the Office profile and make sure the hours of operation are NOT 12:00AM to 12:00AM
Change it to 12:00AM to 11:59PM (or less)
--
rjl

[Reply][Quote]

Sarah Peterson
Posts: 37

Re: 6.1.1 - Basic had an error. Context: leaccount. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 22 Mar 07 9:31 AM

Thanks for the suggestion but our hours of operation have been set from 7:30AM to 6:00PM since we started. But I could see where 12:00AM-12:00AM would cause problems.

[Reply][Quote]

Bob (RJ)Ledger
Posts: 1103

Re: 6.1.1 - Basic had an error. Context: leaccount. Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 24 Mar 07 7:17 AM

Quote:

Originally posted by Sarah Peterson

...

If anybody would be able to offer any assistance that would be great. However, seeing that the post on ITToolbox has been out there for several years without any response and this posting has been listed for quite awhile without any response, I can only assume nobody knows how to address the problem.

If that is the case, then I would just like to mention the frustration of being a customer of a product that has had known issues for over 3 years that have not been addressed in newer releases. It will not score any brownie points here for our company that currently has over 300 employees that have access to the Support client.

In general, until "support" was added to the SalesLogix client app (v6.2.x) I really did very little work/customization on it. The reaso?.. 99% of our clients used support OOTB with zero customization. Now that the Support client (as a seperate app) is DEAD (YES!) in 7.0.x (all of it's "features" are now part of the SalesLogix client) I've not seen any strange issues.

Remember, anyone running any version of SalesLogix that is not 6.2.x or 7.0.x is running an unsupported product. It's time to upgrade.
--
rjl

[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): 7/8/2025 3:16:49 PM