Moin Olaf,

I did it this morning. Now I will see whether it has solved it.

But since we have upgraded our old Windows Server 2003 to Windows Server 2016 we experience also other oddities, where e.g. printer go offline - but only at one workstation while other users have no problem with the network printers. 

I take another cup of coffee and will wait ... [C]

Gruss

Joerg

Hi Guys,

We are using Pmail in a multi-user environment where all of my 15 users are starting their own Pmail instance from the same source at a server share. Works fine so far. Also the system address book is being used and maintained by all users. Now one user experiences problems when saving a new entry in the address book, irrespective whether it is a system address book or a privat one. He could call the address book window and he can make his entries, but when saving, Pmail crashes. This happens not every time. In case I take care and check his account from my machine, it works fine (Admin fingers [;)]). And also on his machine this happens not every time.

At the moment I guess it's a network problem but not a Pmail problem. Tomorrow I will firstly check whether any power saving adjustments are made for his NIC. It seems that his notebook lost the connection to the Pmail files at the server after a certain time. But maybe somebody has another clue.

Nice evening or nice afternoon to our american guys.

Joerg

Same operating system on your PC and his?

[quote user="Brian Fluet"]Same operating system on your PC and his?[/quote]

Yes, W7 64bit on both machines. The difference is that his machine is a notebook, connected to the LAN via docking station. Maybe the power settings on the notebook are more strictly set. This I will check tomorrow.

If a notebook is not on battery, disable power saving options (except maybe monitor/display). Pegasus is not the only application that doesn't like service interrupts due to power saving. Even Microsofts Office has sometime problems while accessing network resources.

bye    Olaf