Dave's Technophorical Times

A blog about Microsoft's Technologies!
SharePoint :: MVC :: ASP.NET :: IIS :: SQL Server :: Visual Studio :: MS Access

When you apply a hot fix to SharePoint 2010 you need to run a command to complete the patch otherwise you will see this message in Central Admin "Databases running in compatibility range, upgrade recommended" under Upgrade and Migration -> Review database status, under the Status column.

To resolve this issue you need do the following.
1. Open an Administrative command prompt. CMD - Run as Administrator, or open the SharePoint PowerShell Command Window.
2. If running just the normal PowerShell Command Windows, change directory to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
3. Run PSConfig.exe -cmd upgrade

More information can be found here: http://technet.microsoft.com/en-us/library/cc263093.aspx

Hotfixes/Cummulative Updates: http://technet.microsoft.com/en-us/sharepoint/ff800847.aspx#LatestUpdates



How to set Favicon to the SharePoint 2010 site?

SharePoint 2010 comes with a orange Favicon and it's present in SharePoint Root Folder\Template\Images [eg. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\]. Open this folder and search for favicon.ico and rename the file to FaviconBackup.ico. Now copy your favicon to this folder and make sure it's named as "favicon.ico". Now restart IIS(open Command Prompt -> IISReset), clear browser cache/temproary internet files. Close the browser and reopen then browse the SharePoint site.

If mulitple sites are hosted in same farm and need to set different favicons for different sites then we have to update Master Page Code. Open the site with SharePoint Designer 2010 and select Master pages -> v4.master. The default.master is still present in SharePoint 2010 for backward compatibility and visual upgrade. But SharePoint 2010 uses v4.master only. Now click "Edit File" link to add the favicon code. If it asks for check out, click yes and continue.

Find and change the path of favicon. Save and close (If you have checked out then you need to check in and site collection administrator has to approve it via Site Settings -> Galleries -> Master pages and page layouts -> Check in and Approve). Now reset IIS/clear browser cache and check.



I had this same issue and the reason why it multiplies is because it's in a Content Editor WebPart (CEWP) as a <Script> when it should be Linked to a document in a library. Basically, copy the <Script> into a Notepad document then save it as Widget.htm on your desktop. Then create a New Document Library called Widgets (sounds good to me!), then add the Widget.htm file to the library. Click in the document and you will see the widget render as expected. Then the copy the URL from the address bar. Add a new CEWP to your web page and then paste the URL into the link section! BTW, I would not include http://mysite in the link, just use everything else it.

Now your widget is safely rendered and it will NOT multiply like magic bunnies.

Hope this helps someone out there! Oh BTW, this issue arrived to me after I migrated a 2007 to 2010 site.

Dave



I have had to do some work on Data List Views recently after migrating from 2007 to 2010 since DataFormWebParts don't really work as they should in 2010, especially when it comes to the DispForm.aspx, for example, especially because (at least I found this) it would not open the DispForm.aspx page in Modal Dialog mode. Plus the New and Edit forms would not open in Modal Dialog either. So I have found a few excellent videos by Laura Rogers that helped me a lot. Basically XSLT Views Rock!

Laura Rogers - SharePoint 2010 Data View and XSLT List View:  http://www.youtube.com/watch?v=r2eODYHp73A

Laura Rogers - Creating Hyperlinks in SharePoint Designer 2010:  http://www.youtube.com/watch?v=-ZBF_J1RWis

SharePoint 2010 - Display list or library on another site:    http://www.youtube.com/watch?v=0SfpgoEUlIw

YouTube Site: http://www.youtube.com/user/WonderLaura67

Laura provides a lot of information so please replay the videos as you will pick up more and more as you put her advise to practice.

Hope this helps someone out there! I know it helped me a great deal.

Dave 



I have had this issue popup a couple times in the last 2 years and it always catches me off guard!

You notice that "all of a sudden" one day that your SharePoint Site is Locked. You can't add anything, change anything, like users or documents. It's all locked! This is usually because a Backup was stopped (or died from a server reboot!) before it was able to complete!

Simple solution that you can run at the SharePoint PowerShell Command Line: Set-SPSite -Identity "<SiteCollection>" -LockState Unlock
More Info here: http://technet.microsoft.com/en-us/library/cc263238.aspx 



After a upgrading SharePoint 2007 to 2010, the UI Version is still set to version 3, which makes it look like SharePoint 2007. In order to update the UI to look and feel like SharePoint 2010 to need to run the following script, which will update all site collections. You should save this as UpdateSPUIVersion.ps1, then run it in PowerShell.

Add-PSSnapin Microsoft.SharePoint.Powershell –ErrorAction SilentlyContinue
$SiteCollection=Get-SPSite("http://<SharePointSiteURL>")
foreach($web in $SiteCollection.AllWebs)
{ 
    $web.UIVersion = 4; 
    $web.UIVersionConfigurationEnabled = $false; 
    $web.update();
}

 



The quick way to get a Quick Launch to open in a new windows is like this! The Gotcha is NOT to use double quotes! Always use single quotes.

javascript:window.open('http://www.bbc.co.uk','_blank');history.go(0);
Good link here too: http://techtrainingnotes.blogspot.ca/2010/10/sharepoint-javascript-in-quick-launch.html

To Open a SharePoint 2010 window as a Dialog such as NewForm.aspx, use this method.

EXAMPLE CODE:
JavaScript:var options=SP.UI.$create_DialogOptions();
options.url='http://techtrainingnotes.blogspot.com';
options.height = 400;
void(SP.UI.ModalDialog.showModalDialog(options))

Put this in one line in the Quick Launch, like this;

JavaScript:var options=SP.UI.$create_DialogOptions();options.url='/intranet/Lists/Issues/NewForm.aspx';void(SP.UI.ModalDialog.showModalDialog(options))


as explained here: http://techtrainingnotes.blogspot.ca/2010/12/sharepoint-opening-2010-dialog-box-from.html

 



Laura Rogers has posted it here!

https://www.nothingbutsharepoint.com/sites/eusp/Pages/data-view-web-part-the-basics-add-a-hyperlink.aspx



One of the basic things you would want to do with SharePoint Designer 2010 is editing the layout of the page. This seems easy enough, but when SharePoint Designer 2010 blocks access to the yellowish parts of the code it becomes quite impossible. This is for a good reason, and can be annoying at when you first use SharePoint Designer.

To get around this issue you need to click on the Advanced Mode Ribbon button. Then auto-magically it's accessible and you can get the job done! 

After the Advanced Button is clicked, the server does some processing and then it allows access, which is evident when the yellowish background is removed! 

Happy coding!



I came across a "File Not Found" error when attempting at access a SharePoint Page that had a custom Web Part. Not a very useful error message to say the least. So, in order to actually get more information you will need to have access to the Web.Config file.

Follow these steps:

  1. Navigate Here:
    "C:\inetpub\wwroot\wss\Virtual Directories\<your web app's virtual directory>"
    1. You can also open IIS
    2. Expand Sites.
    3. Right click on your SharePoint site
    4. Choose explore.
  2. Copy and paste the web.config file (making a backup)
  3. Open web.config using in your favourite editor.
  4. Search for “CallStack” , set this equal to true
  5. Search for “Custom”, set the customerrors = “Off”
  6. Search for “Debug”, set Debug = “True”
  7. Save the web.config file and refresh your page in the browser

 

You should now see the problem in the Call Stack and have enough information to know what the problem is or could be.

When you have fixed the problem you may need to so a iisreset to see the site again. Finally, you will need to revert all of those changes to the Web.Config file so that the user doesn't see "Too Much Info"!

Enjoy!
Dave



The Blogger

Dave Stuart I'm a Developer with a passion for coding. I enjoy the challengers that come with the job! SharePoint is one of my expert areas along with .NET Web Development with MVC and good old MS Access VBA coding. I Blog so that I can remember how I did that way back when; PLUS all this stuff is searchable! I constantly study and run my own business, Dafran Inc. I have passed 22 Microsoft Exams since 1998 when I first jumped on the treadmill of knowledge. I hope that you enjoy this Blog as much as I enjoy updating it. All the very best from Calgary, Alberta, Canada. contact me at linkedin @ dafran.ca

Calendar

<<  November 2017  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

View posts in large calendar

Sign in