If you run into this problem and you’ve checked that your Webclient service is running on your computer, there may be chance that the server running SharePoint has basic authentication enabled. There is a fix for this that needs to be installed locally. You can find the explanation and fix here: http://support.microsoft.com/kb/841215
Hey, hey! That great time of the year is comming (no, not Christmas). It even got me blogging again . It’s SharePoint Conference time in Slovenija. Kompas xnet has put together a great program for this year. In fact so many interesting topics are going to take place that this year the event was extended to 2 days. This year they’re introducing also Business track along with the IT Pro track and Developer track.
There are going to be a lot of MVPs and very good presenters under the same roof, so lectures will be very good. Trust me, I have the privilege of knowing lots of them and I have been to their presentations.
This year I’m also attending as a presenter. I believe with a very interesting topic – SharePoint and Silverlight, which are a very powerful combination.
I will also take the opportunity to launch my new open source project on Codeplex.
When? 24th and 25th October 2011.
Being on the other side of the globe is not an excuse. Some guys, like Joel Oleson and Michael Noel are flying in to present.
If you had installed Microsoft Project Server 2010 on a SharePoint server that had running SharePoint 2010 and afterwards you have uninstalled it you may have came in for a great shock. I know I was. After uninstalling Project 2010 I discovered that
- My Central Admin was gone
- All SharePoint sites were gone (also checking in IIS)
That may be a real shocker. One option is to simply rerun config wizard to have the Central admin site and restore entire farm from backup (you DO have backup, do you?). Otherwise here’s the process on how I recovered all the sites:
Re-run SharePoint Products and Technologies Configuration Wizard
- Run the SharePoint Products and Technologies Configuration Wizard
- Rejoin the existing farm (entering database server and configuration database and farm passphrase of your lost SharePoint farm) – thank God these aren’t deleted
- Central admin site has to be recreated
After the configuration wizard has finished you should see all your web applications back in IIS
Remake manual changes to web.config files
If you were making manual changes (not through SharePoint Object Model) to web.config files of your web applications, these are lost, so you better keep track and remake those changes.
Event though you may have your sites back there is still work to do. If you have custom solutions deployed to SharePoint, you have to re-deploy them. Fortunately these are still stored in SharePoint.
SharePoint service applications are not started and you may receive an error like "There are no addresses available for this application" (in logs, event viewer and of course in the web application.
- In SharePoint central administration open Application Management
- Under Service Applications select Services on Server
- Click Start next to service applications that you wish to restart.
You will also notice virtual applications reappearing in your IIS under your SharePoint Services IIS site.
OMG, also solutions are gone from web applications. Yes you need to re-deploy these as well.
- In SharePoint Central Administration select System Settings
- Select Manage Farm solutions
- You will see that all solutions are (probably) there but none of them is deployed.
- Deploy each solution as needed by selecting the solution and clicking “Deploy solution” and following steps.
After redeploying check your web applications if everything is working correctly. I noticed even though solutions were not deployed, the data, configuration and permissions remained.
If you try to delete a subweb in SharePoint (and you’re sure it doesn’t have any subwebs) you receive an error instead. Errors like “Operation not found”, or “Invalid operation”.
Re-running the SharePoint Products and technologies Configuration Wizard repaired the issue for me.
After you have installed SharePoint 2010 Service Pack 1, you may have noticed that Expand/Collapse in SharePoint Lists is not working. Instead you may receive an error
g_ExpGroupXSLTQueue is undefined
Microsoft has issued a hotfix for this bug. You can request it here:
“On the 16th of November you will have the option to attend a series of interesting lectures prepared by renowned experts who are specialized in SharePoint….” Yay – I’ll be having a session there. You’re all invited!
Lots of interesting topics to attend to along with proimisin culinary experience
This time we use calculated field and filtering list view via URL to create a simple alphabetical filter positioned above or below list view:
After that taking this one step further we expand this example to make a configurable script with some (configurable) styling and displaying the selected filter value:
And with configurable styling we could even simply manipulate the look and feel of the filter.
The same script can be used on multiple lists and views without rewriting the code. All because using the linked content file approach (tip 3 on this page). If you’re eager to use the script and not go through the entire article, there is full script almost at the end of the article.
Not directly related to SharePoint, but since SP2010 is hosted on Win2008 I’d say this would come in handy to SP admins. I ran into an issue a while ago where the server would become unresponsive after applying Windows updates. It would finish installing updates, and after restart it would just hang in step 3 of 3 or at "Applying computer settings" or "Applying user settings".
Even though at some point when I’d managed to logged in and see my desktop it was impossible to start anything service-based (IIS, SharePoint, Internet Explorer,…)
What did the trick for me? Couple of things, not sure which is THE fix, and I’m adding couple more that I’ve found searching the Web.
1. Reboot into safe mode after applying Windows Updates. This avoids any driver/service conflict issue. After successfully rebooted in safe mode, restart to normal boot.
2. Delete temporary files (to find them, open a "Run" window, type %temp% and press Enter.). This removes the chance of having some legacy corrupt update process file.
3. Check disk space on your system drive – no need for explanation there. Patches can be quite space consuming.
4. If you have IIS (if you have SharePoint, then you do), make a small registry fix to enforce service startup dependancy. Detailed instructions here: http://support.microsoft.com/kb/2004121.
Hopefully one of those "fixes" will work also for you if you’re facing the same problem.
If you’ve been surprised when opening a DataSheet view in SharePoint by receiving a message like the one below:
(Below also message in Slovene for my Slovene-SharePoint-using-friends)
Then you’re missing something. The same as me. The support article from Microsoft (located here) explains that we need to do one of the following:
- Don’t use 64-bit Office 2010 or
- if you have to use the 64-bit version, download and install the 2007 Office System Driver: Data Connectivity Components
This goes for SharePoint 3.0/2007 and 4.0/2010
I’ve been involved in some very interesting SharePoint projects lately so I wasn’t taking time to write my blog. Anyway after a while I’m continuing with The Power of CEWP article series. Even though this article is written in SP2007 with minor modifications it could also be applied to SP2010 (but for SP2010 better solutions exist – XSLT without unghosting pages. As always the entire code can be found at the end.