Error in Hyper-V VMs at startup after installation of Backup software

Once the server has started, the VMs are not initiated.

Error displayed:

Error: 0x8007001F

According to Microsoft, this is the explanation:

It is a timing issue with FSDepends.sys and VHDMP.sys . This timing issue occurs when certain programs backup (backup software) installed on computers that are running Windows Server 2008. By default, the value of early FSDepends.sys the register is set to Manual . When any software backup third party carries its driver tape device, the software sometimes can result in FSDepends.sys and VHDMP.sys not initialize correctly.
How to fix follow these steps :

1) Start the Registry Editor.
2) Go to the following registry key: ” HKLM \ SYSTEM \ CurrentControlSet \ Services \ FsDepends ”
3) Under the key ” FsDepends “, change the value REG_DWORD “Start” to “3” to ” 0 ”
4) Restart the computer

NOTE: In most cases you must also disable the tape drive in Windows, restart the OS and after restarting VMs, enabling the unit if necessary.

The following Microsoft link: http://support.microsoft.com/kb/2013544

VS Debug Problem with IE8

I decide to write about a problem that has been opened frequently on ASP.NET official forum which is VS debugger crashes with IE8.

How VS debugger could be crashed with IE8?

If you opened multiple instances of IE8 and you attempt to debug your project, you mostly will have the issue where VS debugger just stops and ignores your break points!

Why was that?

Well, IE 8 has a feature called Loosely-Coupled Internet Explorer (LCIE) which results in IE running across multiple processes.
http://www.microsoft.com/windows/internet-explorer/beta/readiness/developers-existing.aspx#lcie

Older versions of the Visual Studio Debugger get confused by this and cannot figure out how to attach to the correct process.

To overcome this issue, you need to disable the process growth feature of LCIE by follow the below steps:

1) Open RegEdit
2) Browse to HKEY_LOCALMACHINE -> SOFTWARE -> Microsoft -> Internet Explorer -> Main
3) Add a dword under this key called TabProcGrowth
4) Set TabProcGrowth to 0

If you run into the same problem on Vista or newer, you will also need to turn off protected mode.

And then go a head and start debugging your code.

Ref : Weblogs Asp.Net

Configuring MOSS 2007 server to search pdf documents – install and configure pdf ifilters

In this article we will see how to configure MOSS 2007 to search PDF documents.

 

Application Server:

1. Download Adobe PDF IFilters 6.0
2. Start –>Run–>> Services.msc and stop the IIS Admin service. The reason we need to do this is, the IFilters configuration needs an update to DOCICON.XML.
3. Download the pdf icon image   of size 17X17 from the following location and save it as “icpdf.gif” somewhere to the local hard disk
   http://www.adobe.com/misc/linking.html
4. Copy the icpdf.gif to the following location
   “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images”
5. Go the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\
6. Edit the DOCICON.XML by adding the following entry  pdf” Value=”icpdf.gif”/> 
7. Perform an IIS RESET
8.  
9. Go to Search Settings under Central Administration and add the pdf as the new file type 

Indexing Server:

1. Run the IFilters installer on the Indexing Server
   1. Locate and then click the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Search\Applications\GUID\Gather\Search\Extensions\ExtensionList
   2. On the Edit menu, point to New, and then click String Value.
   3. Type 38, and then press ENTER.
   4. Right-click the registry entry that you created, and then click Modify.
   5. In the Value data box, type pdf, and then click OK. 
2. Go the C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\
3. Edit the DOCICON.XML by adding the following entry <Mapping Key=”pdf” Value=”icpdf.gif”/> 
4. Perform an IIS RESET
5. 
6. Go to Search Settings under Central Administration and add the pdf as the new file type
7. 
8. Go to SharePoint Service Provider
9. Click on Search Setting
10. 
11. Click on Content Source
12. 
13. Perform the crawl again
14. 

Data: application/pdf 

1. Upload the PDF documents to the Windows SharePoint Services 3.0 Web site.
   1. Stop and then start the Windows SharePoint Services Search service. To do this, follow these steps:a. Click Start, click Run, type cmd, and then click OK.
   2. Stop the Windows SharePoint Services Search service. To do this, type net stop spsearch at the command prompt, and then press ENTER.
   3. Start the Windows SharePoint Services Search service. To do this, type net start spsearch at the command prompt, and then press ENTER.
   4. Type exit to exit the command prompt.

 Now MOSS is ready to search pdf documents.

Ref : C # Corner

SharePoint “Crawl Log error: Access Denied”

Issue
Windows Server 2003 SP1 introduced a loopback security check. This feature is obviously also present in Windows Server 2008. The feature prevents access to a web application using a fully qualified domain name (FQDN) if an attempt to access it takes place from a machine that hosts that application. The end result is a 401.1 Access Denied from the web server and a logon failure in the event log.

1. Login to the SharePoint server.
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

4. Right-click Lsa, point to New, and then click DWORD Value.
5. Type DisableLoopbackCheck, and then press ENTER.
6. Right-click DisableLoopbackCheck, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. Quit Registry Editor, and then restart your computer.

However, for production environments, DO NOT DISABLE this feature. You are unpicking a serious security check of the OS. If that environment underwent a security audit by a competent security engineer, it would be flagged. You should add a list of addresses you wish to exclude. This makes your scenario work whilst retaining the security check.

1. Login to the SharePoint server.
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0
4. Right-click MSV1_0, point to New, and then click Multi-String Value.
5. Type BackConnectionHostNames, and then press ENTER.
6. Right-click BackConnectionHostNames, and then click Modify.
7. In the Value data box, type the host name or the host names for the sites that are on the local computer, and then click OK.
8. Quit Registry Editor, and then restart the IISAdmin service.  (Or Recycle the App-Pool).

Ref: http://support.microsoft.com/kb/896861

SharePoint Search Crawler Error After Installing .NET 3.5 SP1

I installed Microsoft .NET 3.5 SP1 on SharePoint 2007 today, which was a prerequisite for an updated 3rd party application that we use with SharePoint. After the upgrade, I attempted to perform a Full Crawl but the crawl only took a few seconds and only Access Denied errors were displayed in the crawl log. After investigating the Event Viewer on the SharePoint Search server, the following error was found:

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date:  1/27/2011
Time:  10:29:16 PM
User:  N/A
Computer: SHP1
Description:
The start address http://intranet.contoso.com/ cannot be crawled.
Context: Application ‘SSP’, Catalog ‘Portal_Content’
Details:
Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has “Full Read” permissions on the SharePoint Web Application being crawled.   (0x80041205) For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

After some investigation, A fix was found in KB896861 by adding theDisableLoopbackCheck key to the registry. Once the registry key was added and the IIS Admin service was restarted, I attempted to perform another full crawl and this time it was successful!

Ref : http://support.microsoft.com/kb/896861

Office 2003 and 2007 Office documents open read-only in Internet Explorer via SharePoint

After searching the web I found workaround that should workhttp://support.microsoft.com/?kbid=870853. According this article:

1. Quit all running Office 2003/07 programs.
2. Open register (regedit.exe)
3. Locate and then right-click the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Internet
4. Point to New, and then click DWORD Value.
5. Type OpenDocumentsReadWriteWhileBrowsing, and then press ENTER.
6. Right-click OpenDocumentsReadWriteWhileBrowsing, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. On the File menu, click Exit to quit Registry Editor.

After testing I was able to open file in the Edit mode.

Restore My Active Desktop

1.Click Start, and then click Run.

2.In the Open box, type regedit, and then click OK.

3.Locate and then click the following registry sub-key:

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Desktop\Safe Mode\Components

4.In the right pane, right-click DeskHtmlVersion, and then click Modify.

5.In the Value data box, type 0 (change it from 272), and then click OK.

6.Exit Registry Editor.

7.Refresh the Desktop.