Ray,
the -1 return code: this usually is the case when I'm running Sesame in standalone, doing some development or some such on my laptop. The @Sendmail does NOT like stand alone mode or when I am a client to the office Sesame server through the Internet (at least as I have it set up), but it runs like a champ if my laptop is a physical client on my network at the office.
The -4 return code: this is a recurring error from one computer most of the time (maybe it's all the time on that computer ... I should disable the security software and test it a little bit), and a problem on several other computers intermittently, although if it happens and then we reboot that workstation, it almost always allows Sesame to operate error-free for awhile. But if I get an -4 error on one of these slaggard workstations, and then go run that command button from my newer Win7-64 laptop, it always 'just works'. The 'To, CC, BCC addresses are hard coded in several of these buttons to send alerts to several of my employees throughout the day on various things (although I am reprogramming the hard coding, as I 'get to it', to allow for more flexibility).
On the crashing issue, a couple of the older computers (6 years old? 2gb ram, WinXP) can experience client Sesame crashes several times a day, but then go a few days without issues (usually, as I've mentioned, when printing labels - I think Sesame get's irritated at having to wait for the slow speeds of the label printer and the spooler ... one reason I'm anxious to put a desktop on the network running Win7 with 8gb ram and see if that problem disappears from that network node). But the Sesame server engine will crash sporadically maybe once a week (it's hard to find a pattern - it might happen a couple of times in one day, then not happen again for a couple of weeks). And I have no convincing evidence or argument that it's 'Sesame', and not a hardward issue (network card, network cable, network router, security software, etc) ... except my notional vague observation that the problems increased after moving to 2.5.3 from 2.5.2 (or maybe it was going from 2.5 to 2.5.2). I really don't have a clear enough chronology at this point to be very cogent about it - sorry!
I'll report in once I get some experiential history on the 'muscle fix'.
|