Skip to main content

We have a client who has been running a process for a few months.  Both K2 and MOSS are on the same box.  It's all been going okay until now.


Last week we moved the sharepoint site the process communicates with onto a different web app.  (it used to be http://server/sitename and it's now http://server:port/differentsitename).  This was set as an environment field.


We actually forgot about the process when we moved the site - only noticed when we started getting errors.  Anyway, I updated the environment field and tried to redploy the solution.  I'm now getting an error (in visual studio) saying ...
Deploy started: Project : <project name>
error : Access to the path 'entries' is denied.
====== Deploy: 0 succeeded, 1 failed, 0 skipped =====


I have no idea what 'entries' is.  I'm not using anything of that name I don't think. Have checked and sharepoint, k2 and the db are all running under the same domain user.  there's nothing hitting the event viewer. There's no error in the server output (just says starting session, authenticating <user>, ending session.  It's all a bit odd.  Anybody any ideas?


FYI, we're running bp sp1 (but not 0803) and moss sp1.  All kicking off of processes, updates, task lists etc are done via a asp.net app or web parts - we're not using the k2 task list or anything.  the only communication between k2 and the sharepoint site is the insertion of a record into a calendar list.  (this is where the error was when the site was moved).


Hope that all makes sense. Any ideas would be great.
Thanks
P

Have you tried using FileMon to check for file access errors?

http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx 

This will show up any permissions errors or "file not found's" that may be occuring on a machine level.

 


Thanks Murray, will give it a try.

That worked like a charm - great tool, will remember it in future.  (Though used Process Mon - a later version)


It turned out to be the clients source control system locking the bin and obj folders and not allowing VS to write to them.  Very frustrating!

Thanks for you help.
P


Reply