Visual Studio 6 + Samba 2.2.5 misbehaves.
Hello!
I just noticed 2 problems when using Visual Studio 6 to edit files located
on a Samba share.
1. This file has been modified outside of the source editor.
To reproduce: Create a C++ file and save it on the share. Type some text,
within a couple of seconds it will pop up a message box warning that the
file has changed on disk, do you want to reaload it?
When dismissed the message will appear again at semi random intervals,
saving the file again is also a sure way to trigger it.
2. Windows XP pops up a baloon in the corner with Delayed Write Failed.
Start a new project with it's location on a samba share, create and add a
C++ file to the project. Edit and save the file a couple of times and XP
will pop up warning baloon and log the following message to the EventLog:
{Delayed Write Failed} Windows was unable to save all the data for the
file \Device\LanmanRedirector. The data has been lost. This error may be
caused by a failure of your computer hardware or network connection.
Please try to save this file elsewhere.
The file in question is ProjectName.ncb, dunno what it is used for.
After the message has appared the first time, it will pop up every time
you type text in the editor.
Needless to say, this makes Visual Studio pretty much useless...
What can I do to help debug this?
Regards,
Fredrik
--
It is easy to be blinded to the essential uselessness of computers by
the sense of accomplishment you get from getting them to work at all.
- Douglas Adams
Fredrik Öhrn Chalmers University of Technology
[EMAIL PROTECTED] Sweden
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
This sounds like you have clocks out of sync. Be sure that the time on
your workstation, the Samba server, and any NFS servers that Samba may
get shares from all have clocks that are in sync. I highly suggest
using NTP between all servers. Once you have NTP running on a unix
server, you can convince win2k clients to sync with that server using:
net time /setsntp:unixservername
Mike
On Thu, 2002-08-01 at 05:37, Fredrik Ohrn wrote:
Hello!
I just noticed 2 problems when using Visual Studio 6 to edit files located
on a Samba share.
1. This file has been modified outside of the source editor.
To reproduce: Create a C++ file and save it on the share. Type some text,
within a couple of seconds it will pop up a message box warning that the
file has changed on disk, do you want to reaload it?
When dismissed the message will appear again at semi random intervals,
saving the file again is also a sure way to trigger it.
2. Windows XP pops up a baloon in the corner with Delayed Write Failed.
Start a new project with it's location on a samba share, create and add a
C++ file to the project. Edit and save the file a couple of times and XP
will pop up warning baloon and log the following message to the EventLog:
{Delayed Write Failed} Windows was unable to save all the data for the
file \Device\LanmanRedirector. The data has been lost. This error may be
caused by a failure of your computer hardware or network connection.
Please try to save this file elsewhere.
The file in question is ProjectName.ncb, dunno what it is used for.
After the message has appared the first time, it will pop up every time
you type text in the editor.
Needless to say, this makes Visual Studio pretty much useless...
What can I do to help debug this?
Regards,
Fredrik
--
It is easy to be blinded to the essential uselessness of computers by
the sense of accomplishment you get from getting them to work at all.
- Douglas Adams
Fredrik Öhrn Chalmers University of Technology
[EMAIL PROTECTED] Sweden
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
Mike Gerdts wrote: net time /setsntp:unixservername I think I've been having this problem too -- thanks! Do I need to put that command in a profile so that it's executed at each logon, or can I run the command once only (on each workstation) ... ?
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
On Thu, 1 Aug 2002, Steven Mackenzie wrote: Mike Gerdts wrote: net time /setsntp:unixservername I think I've been having this problem too -- thanks! Do I need to put that command in a profile so that it's executed at each logon, or can I run the command once only (on each workstation) ... ? It's enough to run it once. Regards, Fredrik -- It is easy to be blinded to the essential uselessness of computers by the sense of accomplishment you get from getting them to work at all. - Douglas Adams Fredrik Öhrn Chalmers University of Technology [EMAIL PROTECTED] Sweden
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
On Thu, 1 Aug 2002, Andrew Bartlett wrote: As a basic rule, setting 'deadtime' is a bad idea. Is there any reason to set this paramater? Once upon a time our servers got pretty bogged down during daytime, deadtime and other quick fixes helped alleviate this. With all the hardware upgrades we've done over the last year it might not be necessary anymore, it has just stayed around in our configs out of tradition. I'll remove it and see what happens. Regards, Fredrik -- It is easy to be blinded to the essential uselessness of computers by the sense of accomplishment you get from getting them to work at all. - Douglas Adams Fredrik Öhrn Chalmers University of Technology [EMAIL PROTECTED] Sweden
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
Mathew McKernan wrote: Hi Fredrik, This problem has been found with any server. Whether it be Samba or 2k or NT. I have had this problem with a NT server, as we didn't have a NTP server at the time, I used net time \\server /set /yes in the logon script. Made life a lot easier. I use the net time \\server method at home as I run a mixture of XP/98 workstations and a Samba server. I can't be bothered finding a NTP sync program for 98 workstations *grin*. Remember that with general NT/2k/XP permissions won't allow users to change clock time, so in your Domain Policies/Local Security Policies/User Manager (depending on OS) you need to set the advanced options to allow Users can change system time. By default Administrators and Power users only can. Or setup an NTP server an use 'ntptime' to syncronise them as 'system'. Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
Re: Visual Studio 6 + Samba 2.2.5 misbehaves.
As others have said, this is a time syncronization issue which is not Samba specific. When the file is saved to the server, the timestamp put on the file is the Server's time. Assume for a moment that the server time is ahead of the workstation time. Visual basic will periodically check the timestamp on a file. If the time is newer than when it last wrote to the file, someone else modified it - hence the This file has been modified outside of the source editor. In otherwords, if I last wrote to the file at 6:00, and happen to take a look at it and it says it was written to at 6:01 then I can only conclude that someone else wrote to it. If the server is 1 minute ahead, then it will save the file with a timestamp of 6:01 if I save it at 6:00WT (Workstation Time). That's where your error message is coming from. Novell builds time synchronization into the workstation clients to prevent these types of problems. There's no way to solve it only server side, otherwise it would be part of Samba, Windows NT, NetWare, and pretty much every other NOS.
