Not enough information to diagnose... it could be a ton of things:
A - What vers/sp/build of SalesLogix?
B - is this part of something that was customized
C - etc......
--
RJLedger - www.SlxWizard.comrjlSystems

You are most likely correct, it is usually a mistake in your application
code that was running at that moment. Unlike typical compiled software
the clone vb interpreter will throw those kinds of errors when it come
across application code it can't handle. If you are lucky, you will get
a message that precedes this one that will often give you the line
number in the script and more detail. In lieu of that you can run
saleslogix on a client machine that has visual studio installed and it
will break into the debugger. From this point you often figure out the
offending script.
Some of these errors occur at exactly the same location and can be
simply the result of configuration errors. In these cases you should
reevaluate any setting changes you have made recently.
Vic