7/10/2025 2:29:18 AM
|
| |
| 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!
Forum to discuss general administration topics for SalesLogix (including LAN & remote topics). View the code of conduct for posting guidelines.
|
|
|
| |
| |
|
Re: On Open of SLX 6.2.5 SQL error, "failed to parse SQL at line 330, char 11"
Posted: 17 Oct 07 9:25 AM
|
The script that is failing is System: Global System, the exact message reads;
An error occurred executing global script (System: Global System)
Failed to parse SQL. at line 330, char 11
This error happens on after the user opens SLX and gets the following error;
Error accessing database:
Failed to parse SQL.
If this problem persists, please contact your administrator.
The user exits out of the error messages and cannot do anything in the screens. After closing the client, the above message displays and the user cannot even login. After rebooting the client machine, the user will get the same sequence of errors.
Can something like this happen if the user has her view set to show a group on the right side of screen and that group could have an account with a single quote in the name? We've had trouble with names that have single quotes in the past and thought it might be causing trouble with the initial global process.
|
|
|
|
Re: On Open of SLX 6.2.5 SQL error, "failed to parse SQL at line 330, char 11"
Posted: 17 Oct 07 9:53 AM
|
Actually, I misspoke on the sequence of events.
The errors come up every time the client software is started and in same sequence. The later error just is left on the desktop when you close the software. It shows up when the user tries to do something in the screen prior to closing the software.
Also, the user was doing an email to a group when this started to happen.
I worked with her today and had her turn off the right side listing of accounts and Wait out the blank screen. Once the software came back (it took a long time and it really did look as if the software was hung because the screen was blanked out in many sections), it now seems to be working. Strange!
Anyway, hope all this info helps. But, it sure seems to me that there is a BUG in the client software. |
|
|
| |
|
Re: On Open of SLX 6.2.5 SQL error, "failed to parse SQL at line 330, char 11"
Posted: 17 Oct 07 11:13 AM
|
| I'm not the person who does development, she's out at training this week, but I've been in contact via email. She (and I) think it's somehow related to a group email process for a large group of accounts, some of which have single quotes in their names. And somehow the client startup process seems to be hung directly after this process. Now, what I don't know is whether all of the 759 email processed correctly. Is there some check in the client global script at startup that would break based on a failed process from a previous session? |
|
|
| |
| |
|
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!
|
|
|
|
|
|
|
|