Aaron Reynolds – The ramblings of a tek ‘ed

Ever got this dialog box: "the project location is not trusted" ??

Yeah me too. A recent change in network infrastructure and folder-redirection caused this issue to surface.

The way around it is well documented but sometimes there are other factors to consider.

First, take a look at Microsoft’s fix for this: The Project Location is Not Trusted Dialog Box

Then if you still have a problem like I did, check the location is not in your Trusted sites list in IE (thanks to the following page: http://discuss.joelonsoftware.com/default.asp?dotnet.12.334487.2

I know the author of that page didn’t solve all his problems but removing the network location from my Trusted Sites list sorted out my problem straight away.

AR

I haven’t updated my website much lately – guess I’ve been really busy at work. I’m currently working on some Server 2003 projects and have been playing around with Group Policy, roaming profiles and redirected folders.

These are not new subjects to me but as I tend to do more development work nowadays, it usually means long periods between server work and the things you don’t do every day fall out of your memory.

I had a real grapple with what I initially thought was permissions issues the other day but turned out to be caused by poor allocation in Server 2003 by default.

The situation arose when I was trying to get client machines to create and update roaming profiles (all done in a test environment before going live). The actual error condition was “Not enough server storage space available to process this command” and after trawling about I found the fix to be something going back to Windows NT times and a resistry hack to enable or increase the IRPStackSize. Updated the registry and the problem was solved.

The fix is available here: IRPStackSize Registry Fix

AR