New Tentacle installation (v2.1.3.1223 and v2.1.2.1190) - regular errors in event log

Hi There,

During our evaluation having installed a number of tentacles, we’ve installed a tentacle on a testing environment server - Windows Server 2003 SP2 machine (.NET 4.0 + patch + management framework and Powershell 2.0)

After having some initial difficulty in getting the server to discover the tentacle, communications was establish and the environment health checks passed fine. However when looking into the local appplication event log we see very regular errors being logged. Each one appearing to be the same:

2014-02-21 10:02:35.0440 ERROR Error checking pending timeouts
System.UnauthorizedAccessException: Access to the path is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.__Error.WinIOError()
at System.IO.File.InternalReplace(String sourceFileName, String destinationFileName, String destinationBackupFileName, Boolean ignoreMetadataErrors)
at System.IO.File.Replace(String sourceFileName, String destinationFileName, String destinationBackupFileName)
at Pipefish.Persistence.Filesystem.ActorStateFile.Save(ActorStateDictionary state) in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\Persistence\Filesystem\ActorStateFile.cs:line 90
at Pipefish.PersistentActor`1.Save() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\PersistentActor.cs:line 61
at Pipefish.WellKnown.Timing.Clock.Save() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\WellKnown\Timing\Clock.cs:line 58
at Pipefish.WellKnown.Timing.Clock.Check() in c:\TeamCity\buildAgent\work\cf0b1f41263b24b9\source\Pipefish\WellKnown\Timing\Clock.cs:line 109

For more information, see Help and Support Center at

Any thoughts?

2014-02-21_Octopus_New_Tentacle_installation__v2.1.3.1223_and_v2.1.2.1190__Event_.docx (60 KB)

I’ve found my own error! - The service account was no longer running under the Local System account when it was installed and created the Octopus data folders. When the service account was changed, we should have updated the permissions on the folders to enable access to the new service account.

Thanks for sharing the solution!