Running Sesame 2.5.3 server on Windows XP workstation (11 years).  Most workstations running Windows 7.   

If, in the morning, I open up 'server admin' on the servers, unload my Sesame application, then 'stop this server', then reload the server, usually Sesame on the network will run just fine all day (may one server 'unlock/restart' needed).

But, if I don't do the above (unload/reload at beginning of the day), Sesame clients are likely to randomly and often just disappear from the workstation screen in the middle of a task, and the Sesame client has to be restarted.  Maddening.

I'm sure it's some kind of an issue with my internal network (tcp pipes?) that's causing the client to lose its 'Sesame' communication link with the server.  But I can't figure it out.  I have removed the anti-virus program from the server, and have tested results with a workstation's anti-virus program disabled, but that did not improve reliability.

It's not disabling, but irritating, and it does present ongoing productivity obstacles when I'm working from home, trying to get stuff done on Sesame through the Internet ... thus my original question about 'Sesame life in the cloud'.

ps - Ace, I remember you posting some here a decade ago - am happy to see you still kicking!

Ray,

Yes, understood.  That 'feels' like excellent advice.  (Poking a bit of fun at myself - solutions that were 'no brainers' 10 years ago, somehow now, at 64yrs old, become problematic for this 'well on my way to becoming a no brainer' business owner and past programmer.  I'll mull over whether I have one more 'upgrade in me'.)   

ps - Running Windows XP workstation as server; Running Windows 7 client workstations.  Do I have to be aware of any caveats or preps before upgrading from 2.5.3 to 2.6.4 ?

Are you running the local client using the server name or localhost?

Just curious but either way is still using the network. Now if you launch Sesame standalone and it has the same issue, yes it's not a network issue and could be a programming or data issue. Here again there have been a LOT of changes since 2.5.3 so I would upgrade. The upgrade is a simple process. Just shut down Sesame, Run the update on the Server and ALL clients, and then start it all back up.

-Ray

I upgraded to 2.6.4 today.  I'm still losing connections to the Sesame server engine.  Shutting down the sesame server engine and then bringing it back up is the only thing that improves the stability.   I think I need to run the sesame server engine on a different computer and see if that improves stability (maybe I've got a wiggy hardware issue ... I don't see how that could be, though - it's only a 13year old server running Win XP  )

I'll report what I find out.

All clear swimming with my Sesame Win7 64 desktop workstations.  But the 3 Lenovo Thinkpad laptop workstations will be disconnected by the Sesame server engine, and then have intermittent read/write errors.   Anyone else experience this?

the laptops are connected 'wired'.  Only one of them comes and goes with me, the other two are stationary and wired to the network just like the desktops.

on the Sesame Server screen, it will say "client disconnected 192.168.1.?? (the ip addresses of the laptops), but also it might say 'client disconnected 4PDF"  or "CF226"(part of an inventory part #) ... like the server engine is catching some ephemera transient and mistaking it for a client glitch and so disconnecting it.  when this happens, the disconnect client at the workstation can be accessed and reconnects to the Sesame server, but continues to generate redhighlighted read/file errors on the server engine window, and eventually client gets disconnected again

Interesting discussion. I've had similar issues for years, if not decades. 7:30AM every day I pour a cup of coffee, make sure no stragglers are still connected from the previous day, shut down the server, restart it, and unlock all the databases.

I'm running 2.6.4 on a small cloud virtual Windows Server 2008 and I'll typically get 10-13 users connected at once. Sometimes the server can run all day or even for a day or two without the clients timing out, but then other days I'll have to kick everyone off and reboot 3 or 4 times in a single day.

To this day I am not sure what causes it to lock up and timeout the client connections. I've just learned to live with it. Job security, right? The cloud server is pretty stripped down and there's not a ton of memory to work with, but maybe I shall try tweaking the paging file. Any suggestions on how to troubleshoot this would be most welcome.

Cheers. 

lksseven wrote on Oct 31^st, 2022 at 7:54pm:


You're not seeing what you think you are seeing, as it's likely the desktops also have the same IP's from the day before. If you start Sesame Client, Do something and close out, Sesame server has forgotten about that client(unless you left an XResultSet open but that'll only result in a locked record).

Try this, from a command promp on the laptopt: Run a "Ping -T Servername" where Servername is the name of your server. Just let it run. When you start seeing read/write errors in Sesame, see if the Pings are taking longer or failing.

-Ray