Quantcast
Channel: SharePoint for Dummies
Viewing all 60 articles
Browse latest View live

MOSS 2007 : Data changes are lost after Check in of .accdb file

$
0
0
Let's describe the user issue :

User had a database file stored on our SharePoint 2007 environment. (Database into another Database… Uh ? )
The process to reproduce the user's issue :
-          Put the .accdb in Check out
-          Open the .accdb file
-          Making the changes
-          Saving the file
-          Check in to allow other users to work with the .accdb file

Error got by the user :


Little analysis of the error message : seems that the user had selected an incorrect option while opening the file.


So, I made the same process as the user, but I found a little box that I didn't checked.

-          In Sharepoint, do the Check out to avoid having multiple users modifying the file at the same moment

In the "You are about to check out" popup windows, pay attention that the checked box "Use my local drafts folder" is NOT checked

 Open the file


 In the "Save A local Copy" popup windows, simply click on the Save button..
It is mandatory, as Access had to open the file as if it is on your computer, without any restriction.

-          We are using Office 2010, and at the top of the opened database, you can see those 2 yellow warning bar :

-          Clicking on the "Save to SharePoint Site" button from the Yellow bar will open the "Save to SharePoint" popup windows, showing that the file will be correctly saved to the Site, as expected.

-          System is showing several message windows, and then, we can find the modified database file on SharePoint.



-          Now, let's do the Check in of the document.

-          Now, the document is Check in without any error.



That's all folks


IIS 7.0 & Special Caracters in path of filename

$
0
0
Who was not faced to the error 404 page in SharePoint 2007 ?
Specially when the End User explain that his site is no more working?

Little debug, shows that the EU had the wonderfull idea to create a new folder for his documents (or a document) containing a special caracter : "+" sign.

The workaround that I found, was to rename the folder/file, and ask the EU not to use anymore those special caracters.

Yesterday, I had a post from Fabrice Romelard's blog explaning how to solve this issue, and the root cause of this issue : IIS 7.0 replace the + sign by a space in the URL, but shows the correct URL in your navigator.

The solution is to add into each Web.Config field of each SharePoint Web App, this line :

<requestFiltering allowDoubleEscaping="true" />


Then, I was faced to another problem : where to add this command when the "requestFiltering" is already used for the "requestLimits maxAllowedContentLength" command.



Simply write the section like this :

  <system.webServer>
    <security>
      <requestFiltering allowDoubleEscaping="true">
        <requestLimits maxAllowedContentLength="524288000" />
      </requestFiltering>
    </security>
  </system.webServer>


Hope it'll help, as all found exemple on internet shows all commands one by one, but not in the same Web.Config


That's all folks

How to reset the "AllItems.aspx" page in your Shared Documents Library

$
0
0

I was face to a blank page while accessing Shared Documents Library.

First, checking with SharePoint Designer 2007, I saw that the AllItems.aspx page's size was more than 13000Kb (instead of 1Kb).

Trying to open the .aspx page gave me really special caracters, as if you try to open a excel file with your notepad.
By the way, the end user explained that he was saving his excel file into the SharePoint Site's Document Library.

Don't know why, via excel, it overwrite each time the wrong file : the AllItems.aspx


The solution that I've applied is describe herunder :

1         Into the URL, add at the end "?contents=1" :
         …./sitename/Shared%20Documents/Forms/AllItems.aspx?contents=1
2         Check the "Shared Documents" entry
3         Click "Reset"
4         Test
If not ok (was my case), the go to next step
5         Open SharePoint Designer 2007, and open your faulty site
6         Browse through the structure and expand the tree view "Shared Documents => Forms"
7         Right-click on the AllItems.aspx file, and select : "Reset to Site Definition"


That's all folks 


How to Limit the Self-Service Site Creation to only users of a specific AD group

$
0
0

This week, we are finishing the settings and tests of the mySite part of SharePoint 2010.
We will open the mySite for a bench of test users (about 200) until end of February.
After that, we will open the mySite Self-Service Site Creation to all users of the company (more than 10.000).

So, my challenge was to allow the mySite Self-Service Site Creation only to users that are contained into an AD Group.

There is 3 steps :
-          Creation the AD Group as Global Security Group
-          Set the Self-Service Site Creation for the mySite Web App
-          Configure the User Profile Service Application to allow the AD Group to Create Personal Site


1-      mySite Web Application properties :

In Central Administration, highlight your mySite Web App, and check the settings for :

-          Self-Service Site Creation :
Select the "On" radio button, then validate the settings

-          User Permissions :
Check the box " Use Self-Service Site Creation - Create a Web site using Self-Service Site Creation. "


Then, validate the changes

-          User Policy :

Left as default

-          Permission Policy :

Left also as default


2-      Configuration of the User Profile Service Application :

In Central Administration, select the Manage service applications (from Application Management)

-          Select your User Profile Service Application

-          In People => Manage User Permissions do the following :

Uncheck the "Create Personal Site" for the existing users

Add your AD Group, and select only the "Create Personal Site" permissions


Now, people that are not member of your AD Group will not be allowed to create their mySite.



That's all folks 


How to hide an option into the mySite Edit Profile

$
0
0

Today, I was asked to hide an option from the "Edit Profile" section of your mySite.

So, in Central Administration of your service Farm, under the Application Management > Service Applications, select the "Manage Service Applications" link.
Then, select your User Profile Service Application, and select People>Manage Policies link.

Edit the needed policy, and uncheck the "Show on the Edit Details page" box.




That's all folks


How to change the "Show To" option in the "Edit Profile" of mySite

$
0
0

Yesterday, I was asked to change the default "Show To" option in the Edit Profile section on our production mySite.

Some, had to be removed (check my hide post )  from the list, and most of the changes were to allow the mySite owner to select who can view the concerned options.

The "About me", "Assistant" and "Mobile Phone" entries were concerned by this request to match with our privacy policies.



To set the drop-down menu, changes had to be done twice.

So, in Central Administration, go to the "Manage Profile Service" and select your concerned User Profile.
Then,select the People/Manage Policies.


Find the entry and select the Edit option.



Into the "Policy Settings", you will probably have those options set :


1-      Uncheck "Replicable", and click on Ok on the message windows.


2-      Check the "User can override".
The problem is that the "Default Privacy Setting" is not available.


3-      So, validate the changes with the Ok button at the bottom of the page.


You'll be back on the "Manage Policies" page.

 
4-      Re-select your option that you want to change, and edit it again.

5-      Now, the drop-down menu is available, and simply select the default option:


Now, going back to your mySite, and check that the "Show To" is now a selectable drop-down menu.


That's all folks

Search Service Application : old entries to remove to be accurate

$
0
0
Since last week, I've nearly done all to adapt the Search Crawl of our corporate mySite, so it'll match the ne requirements.

During previous tests last November, some old entries were not able to be removed.
I've set new filters, exceptions, etc …
All done, and always executing a full crawl after each changes.

Then, we had to enable the "NetBiosNamesEnabled" option, as our domain is known in 2 different names.

All was redone and working, except for the crawl.

I was expecting that a DB was keeping trace of the old entries, and didn't clean up that database.
A kind of index.

With the help of a consultant, I've explained with as much details as possible what I've done, and what I'm faced with.

Today, he explained that the Indexer in the Search Service Application had to be reset and the mySite contentdb still contains the wrong "domain" users, users that had been crawled at the time before enabling "NetBiasNamesEnabled".


The only way to get this out of the “system” (read: Indexer) is to reset the indexer.


What is the impact of resetting the indexer?
It depends on how big the indexer files are, how long it will take to build up a new indexer file.
Because with resetting the indexer, the existing indexer file will be deleted, and a new indexer file will be created. It will be empty.
This means for the end user that they cannot perform any search anymore until the indexer file has been build up again.

How to build new indexer file after resetting the indexer?
By running a Full Crawl. And this can take some time, depending on the quantity items that have to be crawled.


So the action plan is :
Reset the index
Do a full crawl






Then, after testing, I saw all the wrong entries removed from the search in mySite.



That's all folks

Single Farm Installation Guide (French tutorial)


How to acces in read/write a checked out document ?

$
0
0
Today, I had to explain to a Site Collection Admin how I unlock a file on his SharePoint 2007 site.
The file was checked out by a user that was no more working in his team.

This post resume the steps I explain to the end-user :

1-      Check that the Icon is in "check out"

2-      Two options:
Ø  Check In : make your changes visible to your colleagues, and create a new version (if the versioning option is set)
Ø  Discard Check Out : will discard changes, and the main advantage, is to avoid making new versions of the document when not changes are made into the file.

Complete info can be found on the Microsoft Support Page


That's all folks 

Error while editing SharePoint file.

$
0
0

Hi,
Today, I'm facing to a pervert error on an Excel file located in the SharePoint Library.
This is the error message that the end-user got :

  
So, I decide to open the document (with Office 2010) and got the same message.
 Then, the file is opened in Protected View :
Then, I choose to "Edit Anyway" :

So, now, let's google a little bit, and the first result is what I need.
First answer is so pertinent, that I test it directly :

  1. Download locally the file on my desktop
  2. Rename the file
  3. Open the renamed file : no more issue
File corruption was the problem.
  1. Delete the file in the SharePoint Library
  2. Upload the new file
  3. Open the file from SharePoint
Now, problem solved.
Thanks to Wayne Fan for the solution, and to PSta for having posted the issue.



That's all folks

RSS viewer webpart in SharePoint 2010

$
0
0

Today I solved the issue concerning the availability of the RSS viewer webpart in our production mySite.

2 steps are needed in our case :

1-      Web.config of mySite :
a.       updated the defaultProxy section inf "D:\inetpub\wwwroot\wss\VirtualDirectories\mysite-uat.acc-bgc.net80\web.config" with :
<system.net>
     <defaultProxy>
          <proxy proxyaddress="http://yourproxyname:80" bypassonlocal="true" />
          </defaultProxy>
  </system.net>

b.      IISRESET & do a page refresh

2-      On ISA Server, add the SharePoint Server (CA Server) to the rule that allow it to access http.
Also, "Allow All Users" for the authenticated mode must be used in the ISA rule.

This will avoid the error message hereunder :


Now, all is working as requested :



That's all folks

SharePoint 2007 : Issues with 'Not Finished' Surveys

$
0
0
Today, I was forced to go into the SharePoint Survey Database to try to "unlock" the not finished surveys.

The problem is due to the misuse of the Survey Button.
End-user think that if we point the fact that the button "FINISH" will really finish the survey, part of them will never click on it, and they'll think that the "SAVE" button will do the same.

At the other end of the chain, I'm facing with the survey result that is not compatible with the number of sites that should be in the survey.

Little search on internet, and this post (http://social.msdn.microsoft.com/Forums/en-US/sharepointcustomization/thread/b9ecc145-9bfc-42a2-ae5a-77416657ea85/) gave me the missing pieces of my jigsaw.
The SQL items that must be changed to force the saved survey to become as finished survey.

-          Step 1 : write down the Survey Name (for me, I have to do the job 3 times…) :

-          Step 2 : open your SQL Server Management Studio and open you DB

-          Step 3 : in your dbo.Lists view, find your survey(s) name.

Used Query :
SELECTTOP 1000 [tp_WebId]
      ,[tp_ID]
      ,[tp_Title]
      ,[tp_Created]
  FROM [SharePoint_Content_shpSurvey].[dbo].[Lists]
  Where [tp_Title] like'%Upgrade%'

                               Note : I've used the 'like' word as my three surveys had this word in their name.

                Result :

Now, I've my 3 tp_ID related to all my Surveys.


-          Step 4 : Let's check the content of the dbo.UserData

Used Query :
SELECTTOP 1000 [tp_ID]
      ,[tp_Level]
      ,[tp_DeleteTransactionId]
      ,[tp_CheckoutUserId]
      ,[tp_LeafName]
      ,[nvarchar5]
      ,[tp_Modified]
      ,[tp_Created]
      ,[tp_ContentType]
      ,[nvarchar4]
  FROM [SharePoint_Content_shpSurvey].[dbo].[UserData]
  where [tp_ListID] ='90A65233-C431-414D-8B19-F14C20F799EF'

                Result :

In this list, we can see the completed Surveys (green box).
If tp_Level = 1 and tp_CheckoutUserId = NULL, then the survey is "Completed".
If tp_Level = 255 and tp_CheckoutUserId is not null, then you've pointed out the unfinished surveys.

Adding this line in the previous query "and [tp_Level] = 255", will give the surveys to modify : 10 rows to correct.



-          Step 5 : now, we are going to set the tp_Level to 1 and tp_CheckoutUserId to NULL

Used Query :

BEGIN TRAN UPDATE    UserData
                             SET              tp_CheckoutUserId = NULL, tp_Level = 1
                             WHERE     tp_ListId = '90A65233-C431-414D-8B19-F14C20F799EF' AND tp_Level = 255 AND tp_DeleteTransactionId = 0 COMMIT


Now, checking the dbo.UserData entries : rows 14, 17 and 21 are now correct



-          Step 6 : Let's check the content of the dbo.Docs

Used Query :
SELECTTOP 1000 [Id]
      ,[CheckoutUserId]
      ,[CheckoutDate]
      ,[Level]
      ,[DeleteTransactionId]
  FROM [SharePoint_Content_shpPortal].[dbo].[Docs]
  Where [ListID] = '90A65233-C431-414D-8B19-F14C20F799EF'

In the green square, you can find the correct values for CheckoutUserId, CheckoutDate and Level columns.
In the red square, values that shows the unfinished surveys.

-          Step 7 : now, we are going to set the CheckoutUserId, CheckoutDate to NULL, and Level to 1

Used Query :
BEGIN TRAN UPDATE    Docs
                             SET              CheckoutUserId = NULL, CheckoutDate = NULL, [Level] = 1
                             WHERE     ListId = '90A65233-C431-414D-8B19-F14C20F799EF' AND [Level] = 255 AND CheckoutDate IS NOT NULL AND
                                                   DeleteTransactionId = 0 COMMIT


Now, let's check by searching the Id of former unfinished surveys :

As you can see, all the values are set as requested.


Now, let's check the Before/After in the Survey site : missing Surveys are now available.

                        


That's all folks

FYI : Sharepoint Designer 2010 cannot edit SharePoint 2007 Web Sites

$
0
0
Dear all,

This mail is only for information purpose concerning SharePoint World.

Opening SharePoint 2007 site with SharePoint Designer 2010 give this message box :

Reason :


Solution : install SharePoint Designer 2007


That's all folks

Data Protection Manager for SharePoint 2010

$
0
0

Today's post will point to a link explaining how DPM SharePoint 2010 is working.

I was asked to recover a single file that was deleted early this month and unfortunately, the versioning is not set.
To recover the file on SharePoint 2007, I need to do those steps :

-          Request a restore of the backup to the SQL Team
-          Mount the restore on our SharePoint 2007 test environment
-          Browse the DB and extract the file
-          Copy the file back in production.

Lot of energy for a single file.

Then, I was asked if I have an idea for our SharePoint 2010 production platform to avoid this kind of issue.
I pointed 2 options:
-          Set the versioning by default
-          Use of Data Protection Manager for SharePoint 2010.

I found a nice blog From The Field explaining the DPM process.


That's all folks


How to Open .pdf in your browser with SharePoint 2010

$
0
0
Hi all,

Today's issue came from the complain of a user as he was not allowed to directly open a .pdf file in his browser.
The only solution was to download the .pdf (even if it is set as Read Only) localy, then open it.

I found this well explained post on dmitry's blog.

I've tested and approved the Second Solution, via PowerShell Script :

[CODE]
$WebApp = Get-SPWebApplication http://webapplication.domain.net
If ($WebApp.AllowedInLineDownloadedMimeTypes -notcontains "application/pdf")
{
Write-Host -ForegroundColor White "Adding PDF MIME Type..."
$WebApp.AllowedInLineDownloadedMimeTypes.Add("application/pdf")
$WebApp.UpDate()
Write-Host -ForegroundColor White "Added and Saved."
} Else {
Write-Host -ForegroundColor White "PDF MIME Type is already added."
}
[/CODE]

Do not forget to change the Web App URL at the first line, to match to your Farm.


That's all folks



PEBKAC story

$
0
0
Today's story is only to show how this product (SharePoint) is known by the end-users.

When they do modification into their documents, and the result is different as expected, it is always SharePoint's fault.

So, today, a colleague of mine called me :
- Hey, Mr SharePoint. There is a problem. Can you check ?
- Yes, what is the problem - I said.
- I've change the category of my document, and it is gone from SharePoint.
- Ok, let's check in explorer view (Documents are still on SharePoint 2007 platform).

... Of course, the document is in the library.

- So, what have you done ?  -- I asked.
- I've changed the category, like this (he saved the doc on his laptop, then delete it from SharePoint, and upload it again)
So, my colleague repeat what he does previously, and I checked all the settings he choose, specially the category.

Then, he said, like a winner : "Look, my doc is not there !!!"

- Yes, but check the next category .... you'll find it !!!!

So, SharePoint made what he was asked to do.
The used category was not the same as the expected one. Instead of "IIS 7.0", the selected category was "IIS 7"

So, double pay attention to the typo when creating categories.

Now, my colleague's nickname is "PEBKAC"

SharePoint 1 - PEBKAC 0



That's all folks

How to Apply Cumulative Updates and Avoid Issues

$
0
0
-->
Hi all,

The last few weeks, I was busy in patching our SharePoint 2007 and 2010 farms in test and prod environment.
Of course, I faced several issues, but now, I can say that all farms are up-to-date until Feb 2012 CU.

I can warmly told you to monitor available space on your SQL disk, and the Errors in your Event Viewer for the lack of access rights on the DB's.

Part 1 : Procedure followed to apply the CU

First of all, write down the complete list of your servers of all your farms.

I've 3 environments : PROD, UAT (should be as close as possible to PROD) and Test.
Test is only used for big changes, or in standalone.

PROD and UAT are very important, as if UAT pass the tests, we are allowed to apply the changes in PROD.
This procedure is for the patch, adding new feature, and in this case : allow the end-users to test their migrated sites and to fill the survey.

Doing this, we were able to point out the sites that were customised via SharePoint Designer in 2007.


Now, let's go for the CU process :

STEP1 :
-          Download and prepare the binaries of the CU that will be needed for your patching process.
-          Install the binaries on all your servers in the same Farm. (proceed farm by farm)
-          At the end of this install process, do not click on the message box : "Do you want to reboot to finalise the installation of this package?"
Sometime, this message was displayed, sometime not… Strange…
-          When the binaries are installed on all servers, click on "OK" or "No", following the end message that you got.

STEP 2 :
-          Open the "Configuration Wizard", click "Next", then "YES"
-          And WAIT !!!!
-          Do same operation on all the remaining servers of your farm
-          When all servers are at the same step, go to your CA, and press "Next"
-          When the Wizard is successful, do not click on "Finish", but continue the Configuration process to the next servers, one-by-one.

STEP 3 :
-          On the CA, click "Finish" and check your farm version (System Settings è Manage Servers in this Farm
-          Check the Version, and the status of your servers in the farm. (in this example, 2 servers are upgraded, not the 2 others)

-          Check the Upgrade Status via Upgrade and Migration è Check Upgrade Status





Part 2 : Errors found

Case #1 : Event 3760
The account issue occurs specially on our TEST environment, as DB's are copied from prod, removed and replaced for test purpose.

Case #2 : Event 3758
SQL disk-volume was full.
Solution is to move some DB's to another volume, but SharePoint Services have to be stopped.


Case #3 : Database is deleted, but still listed in SharePoint 2010 CA
I also had this Event 3760, same error as in case #1.
The difference is that the concerned DB was deleted from SQL disk, but was not deleted from SharePoint CA.
So, I removed the entry via Application Management è Manage Content Database, select the related Web Application, and then delete the missing Database Name entry.




Part 3 : used tips

-          If you have the status "Upgrade Available" in the "Farm Information" page, you can always execute this command from your BIN folder (<drive>:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN) :
psconfig -cmd upgrade -inplace b2b -wait
               or
            psconfig -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

In my example, I had to wait longer than in the other farms, as lot of DB's were present, and to run                                                the second psconfig command on the last server.

-          When you've installed the binaries, and you need to install again the CU, you can force it's installation via the command line :
<filename>.glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1

-          In the configuration Wizard, if there is some installed patches shown as "Missing on <servername>", you can use this PowerShell command :
Get-SPProduct -local
            Then, press "Refresh" in the Configuration Wizard".

If you still have issues, please check the created logs, and the Event Viewer.

Doing this let me update all my servers until Feb 2012 CU, in SharePoint 2007 and 2010.



That's all folks.






How to list all the Site Collection Admins into a specific Web Application in Shp2007

$
0
0

Hi all,

Today’s challenge, is to list all the SCA’s of a Web App.

With google, I found a nice simple post on "The Frog Pond of Technology" with a little powershell script.
Then, I found a link to the Brian T. Jackett TechNet Script Repository , and tested his script, with a little change, explained by Tasha’s feedback in the first link (I got the same blank names).

So, hereunder is the script that I’m now using to grab all the SCA’s in the needed WA.

########################################################### #SP_Display-SiteCollectionAdmins1.ps1 -URL # #Author: Brian T. Jackett #Last Modified Date: Mar. 25, 2011 # #Display all site collection admins for all site collections # within a web application. ########################################################### [void][System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SharePoint') #DECLARE VARIABLES [string]$siteUrl = $args[0] function GetMissingParameter { $script:siteUrl = Read-Host "Enter Site URL" } ############ # MAIN ############ #IF MISSING PARM FOR SITE URL, ASK FOR INPUT TO FILL if($args.length -eq 0) { GetMissingParameter } $rootSite = New-Object Microsoft.SharePoint.SPSite($siteUrl) $spWebApp = $rootSite.WebApplication foreach($site in $spWebApp.Sites) { foreach($siteAdmin in $site.RootWeb.SiteAdministrators) { Write-Host "$($siteAdmin.ParentWeb.Url) - $($siteAdmin.Name)" Write-Output "$($siteAdmin.ParentWeb.Url) - $($siteAdmin.Name)" |Out-File -encoding default -append } $site.Dispose() } $rootSite.Dispose()


nb: added the output to a file



I didn’t test this script in SharePoint 2010, but it is said that this script in object model will work for 2007 and 2010.


That's all folks.

How to reinstall SharePoint 2010 on previous uninstalled SharePoint 2010 server

$
0
0

Voilà, I finaly succeded to join the farm with my server.


But now, the story, and how did I solved my issues :


At the begining, the Service Farm had 2 virtual servers.
I was asked to move a physical server from our Collaboration Farm to our Service Farm.

So, as recommended by Microsoft, I've removed the SharePoint 2010 server from the Collab Farm, and tried to join the new farm.... without any success.

I made several attemps, and all were unsuccessful.

Then, I removed completely all the SharePoint 2010 products, patch, CU, registry keys, with always the same punishment : 

“The install progress conflicts with a previously installed Microsoft Office 2010 Server product”



I google for this error, and I found this first blog, from Chad Schultz :



So, I checked again and again, and I still had the Setup Error message box :




I continue my research on google, and found academicjargon's site, with a reference to Chad's post.
Really interresting, as Chad's solution didn't solved his problem, as mine.

The solution was to do Chad's changes, and this one too :
Turns out, you should also do this: Delete the Registries for "WebApps" that appear here:
HKEY_CLASSES_ROOT\Installer\Products\


I  re-run the Prereq, and the install of SharePoint 2010 was started with success.

... Yes, was started ... as I has some patch missing on all 3 servers of my Farm :

KB2512800
KB2553048
KB2553050

Of course, my 2 original servers are patched at level 14.0.6117.5002, as all my other servers in the other farms located in Production and Development domains (near 15 servers).




So, yesterday, I solved KB2512800 and KB2553050 by executing the Microsoft patch on the new server.

Applying the last KB was still unsuccessful for me:






So, this morning, I decide to knock-out this KB-issue.

After more google-ing, I found a strange procedure concerning “Known issues when you install Office 2010 SP1 and SharePoint 2010 SP1”, and concerning the “User Profile” service that must be started:


Quick check on my Central Admin GUI, and I started the User Profile Sync Service, that was stopped.
I execute the KB2553048 patch, and in the “Configuration Wizard” interface, I saw the errors removed after pressing the refresh button : YES !



KB2553048 patch was also executed on my remaining server, and the install procedure follow its way as expected.

By the way, I had another error in the step 3 of the installation : “Cannot connect to the database” ….
Little run to the SQL Team, check of the access rights, and all is ok for my install account.


As mentioned into the error window, I decide to plunge into the .log to find out the problem :

 ******************************************************************************************
07/24/2012 09:48:59  10  ERR                              Failed to connect to the configuration database.
An exception of type System.FormatException was thrown.  Additional exception information: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
System.FormatException: Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
   at System.Guid..ctor(String g)
   at Microsoft.SharePoint.Administration.SPFarm.GetInstalledProductIds()
   at Microsoft.SharePoint.Administration.SPFarm.EnsureCurrentServerProductsMatchFarmProducts()
   at Microsoft.SharePoint.Administration.SPFarm.Join()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()
 ****************************************************************************************** 


So, Google save me again, and I found the solution into Patrick Lamber blog.

Check of the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server extensions\14.0\WSS\InstalledProducts ,

and I had the same entries, and the most interesting one, is the last with value ‘0’.



I checked if I had any Office Web Apps installed binaries (none were present on my server), and I simply deleted the ‘0’ key.

nb : I think that this key, on my server, was the remaining of the previous SharePoint 2010 install. A forgotten key left there by the uninstall.


Then, launch again the Configuration Wizard, and I was able to join with success the Farm.



Now, I’ve my 3 servers into my Service Farm.
Need to setup this new server.




That's all folks.


Post SharePoint 2007 to SharePoint 2010 Migration Issues/Solutions

$
0
0

Today's post will be focused on the issues reported by the end-users when using the new SharePoint 2010 environment.

Hope this will help.





1.    How to choose to open your documents in the browser or in the client ?
(client is by default)

This is the steps to follow if you want to switch the way to your documents : in the browser (default) or in your local Microsoft Office Client.


On the Library Level :
1.       Select the document library
2.       In the ribbon, select "Library" under  "Library Tools"
3.       Then click on "Library Settings" at the right end of the ribbon








e.      Select "Advanced settings" under the "General Settings" column


f.        Select "Open in the client application" to open all the documents from the Library into your local client application (Word, Excel, PowerPoint, Access)


g.       Validate the changes by clicking on "Ok" at the bottom of the page.


On the Site level (all documents in all document library will be affected) :

a.       Select "Site Settings" from the "Site Action" drop-down menu :


b.      Select "Site Collection Features"


c. Activate the "Open Documents in Client Applications by Default" feature



2.    Error in the Logo URL

If the <Company> Branding Logo shows a red cross icon, you have to manually remove the link to the missing logo.


1.       Select "Site Settings" from the "Site Action" drop-down menu :


2.       Under the Look and Feel menu, select the "Title, description, and icon" link


3.       Remove the referenced link to the missing logo, then click OK :



3.    Document bigger than 10Mb cannot be opened in the browser:

Any document bigger than 10Mb cannot be opened into your browser.
Do select to open in your client application (Word, excel, etc…) via the drop-down menu of the file :




4.    How to survey your site usage ?

a.       Site Actions è Site Settings


b.      Site Collection Administration è Storage Metrics


c.       Total size is detailed on the page :



5.    Unsuported Features
Due to Microsoft limitation, all the features available in the Office application are not implemented into the Excel SharePoint Web Services.
In this case, please open your document in your client application (Word, Excel, etc…)


The Excel Service used to open an excel document in the browser is not fully compatible with all the functions/options available in the Excel Client.



6.    How to hide the Quick Launch menu

Via Content Editor Web Part Editor :


1.       Select "Edit Page"



2.       Add a new Web Part


3.       Select "Content Editor" Web Parts from the "Media and Content " Categories, then on


4.       Click on the "Add" button to validate your choice


5.       Click on the link "Click here to add new content"


6.       In the right part of the ribbon, click on "HTML => Edit HMTL Source"




7.       Add this code, then click on "Ok" :

 <style type="text/css">

/*--Hide Quick Launch Panel--*/
#s4-leftpanel{
display:none

}
.s4-ca{
margin-left:0px
}

</style>

8.       To stop editing, click on "Page" in the ribbon, then "Stop Editing"


Via the SharePoint 2010 Web Interface

1.       Select :  Site Actions è Site Settings

 

2.       Select "Tree View" in the "Look and Feel"


3.       Uncheck the radio button "Enable Quick Launch", then click on "Ok"




That's all folks.
Viewing all 60 articles
Browse latest View live