State file not saving to Redundant/Backup Server in Lookout 6.2

[JPhillips]

I have my server process state file set to save the the backup server every 5 minutes. I noticed an alarm recently saying the state file could not be saved. I am able to map, from my server, to the folder on my backup server where I want to save the state file, but when I go into Lookout and 'modify process' and try to browse to this folder I get the error shown in the attachment.

Why can I map to this folder in Windoes Explorer with no problem but not browse to it in Lookout? 

I am running Windows XP Pro SP2, and Lookout 6.2.

[erblock]

Hi,

My guess is that you have proper share permissions set, but not proper file permissions.  When you map in Windows Explorer you are using share permissions.  When you setup file writes in lookout you are maybe using file permissions?  (you didn't specify and I can't tell if that is a share name or directory name after the machine name).  There are other things that can cause this, especially your DNS setup on the machines.

Hope this helps...

Ed

[JPhillips]

The name after the computer name is the share name (I mapped to the folder on the redundant machine). The DNS info is antered manually and is identical on both the redundant and main server machines under the TCP/IP properties. Basically, I set up full control permissions for the folder containing the state file under the 'sharing' and 'security' tabs. This had been working fine for a long time and then suddenly stopped.

[Ryan.S]

I think this error is reported by Windows.

Try to input \\primary2\Lookout\Processes in Run, can you access this folder and copy files to it?

Or you can try to save a file from Excel to that folder, let's see if you get the same error too.

[JPhillips]

Ryan,

As you typed,

"Try to input \\primary2\Lookout\Processes in Run, can you access this folder and copy files to it?" Yes

"Or you can try to save a file from Excel to that folder, let's see if you get the same error too." I created a file in Excel and saved it to \\primary2\Lookout\Processes with no problem.

I can manually copy the state file from the main server to the processes folder on the redundant server - it just won't happen automatically through Lookout.

When I go into the properties dialogue box for the server process file, when I click on browse to select where I want to save the state file it defaults to the local processes folder and I cannot even see the mapped drives.

When I do the same thing in Excel, I can see the mapped drives.

[Mike@DTSI]

Is Lookout running as a service?  If it is, check that the share has permissions for the User Account that Lookout is using. 

Good luck,

Mike

[erblock]

"The name after the computer name is the share name (I mapped to the folder on the redundant machine). The DNS info is antered manually and is identical on both the redundant and main server machines under the TCP/IP properties. Basically, I set up full control permissions for the folder containing the state file under the 'sharing' and 'security' tabs. This had been working fine for a long time and then suddenly stopped. Ok, so have you checked the NTFS permissions for the physical directory of the share location."

OK...so you have set the NTFS permissions in the share's physical directory.  Now you need to also make sure that the share permissions also allow writing by the user Lookout is running under (Mike has a good point on the service option...so check this also.)

Bottom line is you must make sure that the account Lookout is running under has both share and NTFS write permissions AND make sure the Computer that is hosting the state files and share allows remote logon by the user Lookout server is running under (local security settings for the state file host.)

Message Edited by erblock on 01-16-2009 08:27 PM

[JPhillips · Accepted solution]

---

Mike@DTSI wrote:

Is Lookout running as a service?  If it is, check that the share has permissions for the User Account that Lookout is using. 

Good luck,

Mike

---

Mike, 

Lookout is running as a service and that is where I resolved the problem. I had the service set up for Log In As: "Local Account", so I changed it to Log In As: "This Account" and entered the specific account that had full access to that folder.

This had been set up this way for quite some time and was working, so I am not sure what caused it to stop. The user I have logging on is set up as an administrator on the server and the redundant machine which is why I chose the "Local Account" in the services set up.

Thanks very much for pointing me in the right direction!

Thanks very much for your input as well erblock and Ryan!

[Mike@DTSI]

No problem, glad it works.

Mike