Personal views in site migration using Import-Export commads

Personal Views does not get imported/migrated when we do a site import-export on the sub-site or site collection level.

This is a known issue with the product, however, Microsoft doesn’t have any technical reference for this other then the discussion on the Technical Forum.

Other problem occurred with import exports are:

•           All personalization’s are completely lost (personal views, workflows and alerts) 

•           Various customizations are also lost

•           Sites based off old site templates are not handled

•           During import, some files are dropped off due to the blocked items list.

•           There are some versioning and security issues as well.

We have tested the above specification in our environment and results are same.

Error '0x80040e09' occurred during full-text index population for table or indexed view '[DB Name].[dbo].[CurrentPostCombined]': SQL Full Text Search Continued.

In continuation of the Full text search articles discussed before Article 1 and Article 2. Today we finally cracked the resolution of the error message below with the help on MS.

Crawl Log

"2012-08-31 19:01:39.11 spid19s Error '0x80040e09' occurred during full-text index population for table or indexed view '[DB Name].[dbo].[CurrentPostCombined]' (table or indexed view ID '207548023', database ID '15'), full-text key value 0x0000000000ADD0C4. Attempt will be made to reindex it.

2012-08-31 19:01:39.11 spid19s The component 'sqlfth90.dll' reported error while indexing. Component path 'C:\Program Files\Microsoft SQL Server\90\COM\sqlfth90.dll'."

Error log

2012-08-31 19:05:38.15 spid137     Error: 7683, Severity: 16, State: 1.

2012-08-31 19:05:38.15 spid137     Errors were encountered during full-text index population for table or indexed view '[DB Name].[dbo].[ArchivePost]', database 'ngservices' (table or indexed view ID '1813581499', database ID '15'). Please see full-text crawl logs for details.

Error ‘'0x80040e09' indicates Permission was denied for the account running SQL Server Full-Text Search, hence account will need elevated credentials.

RESOLUTION:

Use a low privileged Domain account to run SQL Server Full-Text Search service and restart the service. Please have a look at the following article for more information http://msdn.microsoft.com/en-us/library/ms143504(v=sql.90).aspx

In our environment the SQL Full text search service was running under Local system account. Changing it to run with the SQL Account resolved the issue.

We monitored the file size and it stopped growing.

Hope this helps you to resolve the issue in your environments.

There was an error opening this document. The selected file cannot be found

Problem Description:

When you print the multiple PDF files in Microsoft Office Outlook 2007, you receive the following error message from Adobe Reader:

"There was an error opening this document. The selected file cannot be found."

Resolution:

To resolve this issue, apply the following update: http://support.microsoft.com/kb/2276479  

After you install the hotfix package, follow these steps to enable the hotfix:

Click Start , click Run , type regedit in the O pen box, and then click OK.

Locate and then select the following registry subkey:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options

On the Edit menu, point to New , click  Key , type Attachments , and then press ENTER. 

Locate and then select the following registry subkey:

HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Attachments 

On the Edit menu, point to New, click DWORD(32-bit) Value , type FileTrackIdle , and then press ENTER. 

Right-click FileTrackIdle , and then click  Modify.

In the Value data box, type 5000, and then click OK.

Note If the issue persists, increase the value data by 1000 until you can successfully print all the PDF files. 

Exit Registry Editor.

Note: Before making any changes in the registry, I would request you to take the backup first and then make the changes.

How to back up and restore the registry in Windows XP

http://support.microsoft.com/kb/322756

Please let me know in case of any queries/questions regarding the above mentioned information. I would be more than happy to help you as well as resolves your issues, Thank you.

Acrobat cannot access the network. Please verify your computer's network connection and try again.

Consider the following scenario:

·         You create a French site collection in SharePoint Foundation 2010.

·         You upload a .pdf file to a document library in the French site collection.

·         You check out and edit the file.

·         You try to check in the file.

In this scenario, you receive the following error message:

Acrobat cannot access the network. Please verify your computer's network connection and try again.

If you are facing the above the scenario then Microsoft has already published the resolution for this and here is the link for it: http://support.microsoft.com/kb/2597136

Install the above mentioned hotfix and the issue will be resolved J

I would like to also mention that this hotfix has also fixes lot of issues and you will get a list of those fixes in the above mentioned provided link. Thank you.

Security Management of SharePoint Sites in SharePoint 2013.

Security management of SharePoint sites in SharePoint 2010 has been a bit ‘klugy’, unfortunately, leaving a lot to be desired by both the users and the administrators. Requesting access to a resource or granting access to a resource should not be confusing. In fact, managing security for a site is one of the most fundamental aspects of SharePoint and should be easy and straightforward so you can move on to more pressing things that require your attention. 

The following are a few of the challenges in SharePoint 2010 currently: 

● When site owners are granting rights to other users, they don’t understand which permission level to grant to the other users.
● Once a site owner adds a person to a SharePoint group, they generally don’t understand the rights they are granting that person.
● There is no simple way to figure out who currently has access to a site.
● Once an access request gets submitted by a user, it disappears into oblivion. There is no way to find out the status of that request (aside from emailing or calling the site owner).
● There is no one place where a site owner can go to manage pending access requests.

The SharePoint product team set out to focus on these shortcomings and build a better sharing mechanism in SharePoint 2013. 

When a user doesn’t have access to a site and tries to navigate to it, they are presented with the request "Let us know why you need access to this site." Makes a lot of sense, doesn’t it? It helps the user articulate why they need access when the request is sent, rather than requesting the access and then having the site owner ask this same question in return. See the image below.
                             Figure 1: Why You Need Access
 
This conversation component is visible to both the user who is requesting access and the owner(s) in charge of granting access to the site. It’s a great way for all parties involved to keep on top of the status of the request. The eventual result of the request and the action taken by the site owner is then archived for later reference as needed. 

For the scenario where the site owner wishes to invite folks to the site, it is a simple straightforward process. The site owner clicks the Share link on top left of the site and the dialog appears showing who the site is currently shared with and the fields to invite others to the site. See the Figure 2 below.

                                 Figure 2: Share Dialog Box

Once the site owner decides who to invite and what permission level to grant them, those people get an email notifying them regarding the invitation. This process is pretty straightforward and has worked the same way (but now with a better interface) in SharePoint 2010.


With Permissions from SharePoint Pro.