The other day I was assisting a client changing the URL to their SharePoint environment. They are also running PWA under this site. The name change went very smoothly and I thought everything was running great. I had removed the old URL from the AAM and set the old site to redirect in IIS so anyone typing in the old URL would be taken to the new one.
My joy at the success was short lived. Shortly after completing I got an email that user were getting errors when trying to upload files, view/edit file properties, pretty much anything with a file in a document library. They were getting the error "File not Found". I tested it out myself on the root site and it worked fine, I asked for examples and they were only have the problems on the PWA Project Workspaces. I dug into the SharePoint log files and apparently something in PWA was still referencing the old URL. I thought to myself, great, do I need to leave the old site running to? Doing some searching, I found this post that solved the problem.
Apparently PWA puts an absolute URL in the content databases. If this doesn’t exists you get the error. The good news, you don’t need to modify the content database (something you should never do anyways). Even better, the site doesn’t even need to be running, just add the URL back into AAM (even if the site doesn’t exists in IIS..or in my case is redirecting) and everything goes back to working as expected.
Tags: SharePoint, PWA
Powered by Qumana
How many times have you had an unsuccessful SharePoint deployment? Being on consultant you would be surprised how many times I’ve heard a similar story to: "We have SharePoint, we installed it and because of [insert reason for failure here], it didn’t go well. Will you come in and help us implament it correctly this time."
Well, recently Joel Oleson wrote an article for SharePoint Magazine entitled "Avoid Newbie Mistakes: 10 Steps to Successful SharePoint Deployments"
The 10 Steps Joel gives are:
- Confront Reality
- Create a Governance Plan
- Get an Exec Sponsor
- Create the Dream Team
- Build Services not Stuff
- Define Clear Policies and Standards
- Invest in a Scalable Information Architecture
- Don’t forget Change Management
- Adoptoin is What Counts
- Keep it Simple
For all the details and Joel’s expanded explanation of all these points and how they assist with your SharePoint deployment. Head over to SharePoint Magazine and check out his article.
Tags: SharePoint, MOSS, WSS, Deployment
I was setting up NLB on Windows Server 2008 today and encountered this error: “Attempt to install Network Load Balancing failed with error code 0×80070643. Fatal Error during installation” Upon Googling the error (no, I’m haven’t been converted to Bing quite yet), I didn’t come up with any direct hits, although I did find this blog post on installing MSMQ with the same error code.
The long and short of it is that to install some features on Windows Server, it looks like you need to disable the User Access Control (UAC) first. The steps to disable it are (as given in the aforementioned link):
1. Go to Control panel and click User Accounts
2. Select User Accounts and click Turn User Account Control on/ Off
3. Un-check the check box beside User Account Control
4. Close the User Account Window, reboot the computer and try to install your feature again
These steps worked beautifully for me and allowed me to proceed with installing and configuring NLB for my servers. As was mentioned in the blog as well, once you have installed your features, it is safe to re-enable UAC on your servers if you would like.
The moral of the story, if something isn’t working quite right in Windows Server 2008, try disabling UAC before you try anything else.