IIS Manager Snap-in is empty on your SharePoint Server 2007

If you open IIS manager snap-in on any of your SharePoint servers and it  appears to be blank, the Administrator might not like to see that.


However, Microsoft has confirmed this as a problem and has provided a hotfix for it. This problem can occur for any process that uses ADSI (Active Directory Service Interfaces) to access IIS.


Now there is a temporary fix - An iisreset

Or permanent fix - Install this hotfix KB946517


The hotfix should also fix these events in the event log

- Event ID 6398 
- Event ID 6482 
- Event ID 7076 

Relief :)

How about upgrading to Windows Server 2008 R2 ??

It wasn't an option. GP 2010 and SharePoint 2010 VHDs are out and the pre-requisite was the R2. We were one those who installed the new Windows Server 2008 and thought it would run for the next few years. But at this point we needed an upgrade (as I said, it wasn't an option.)

So, I recently upgraded Hyper-V virtualization server from Windows Server 2008 to Windows Server 2008 R2.

Without making it dramatical, let me get to it. It was easy with all the help from Microsoft KB articles. However, it needed patience as it was an effort - one step at a time.

We had Windows Server 2008 Standard SP1 - Full Installation, running Hyper-V version 6.0.6001.17101. (that's Hyper-V in Beta) and I had many saved state virtual machines.

The ideal upgrade path was:

1. Shut down all Virtual Machines (If you had snapshots you want to be more careful during the upgrade)
2. Upgrade Hyper-V engine from Beta to RTM (version 6.0.6001.18016)
3. Upgrade to Windows Server 2008 R2
4. Re-configure every Virtual Machine. Make sure you have written the configuration of your virtual servers running on Hyper-V

Here are the links that supported me to have a smooth upgrade:

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

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

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

Error 1606: Could Not Access Network Location %APPDATA%\

I was installing Symantec Antivirus on one of the client machines today when it prompted me the error (noticed on Windows Vista). I then Bing'd it to find out that this issue appears when the Shell folder of the logged on user has incorrect entries.
It might be the case with any installation and not just Symantec. I recommend you to backup the registry before trying this out.
These are the steps to fix it:

1. Click Start > Run > regedit.exe
2. Locate the registry key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\
3. Delete the entry which shows the error message

Cyberoam: It's Powered, Still Cannot Ping Cyberoam

Navigate to Firewall > Local ACLs
Tick the ICMP check box in the LAN zone under Network Services

Cyberoam: Does It Act Funny?

You are trying to login to the Cyberoam client using the web browser and it goes into an endless "please wait logging you in" session

Sometimes restarting the Cyberoam appliance will do the magic.

Breakpoint Will Not Currently Be Hit

Ever hit a hurdle debugging a .Net Application? Especially "Breakpoint will not currently be hit. No symbols have been loaded for this document." This is the most deadliest of all. I say this not because it is tough to overcome it, but because it really destroys your productivity. I usually call such hurdles "Productivity Roadblocks"

What CAUSES the Breakpoint will not currently be hit?

This happens primarily because either the .pdb file is not present, there is a mismatch between the .pdb file and the source, or the .dll file that you wish to be debugged has not been loaded.

Is there a RESOLUTION?
Of course there is there are. You may want to try these in sequence as mentioned:

1. Set the configuration option to Debug in the Configuration Manager
2. Delete the .pdb files in your bin folders > Recompile the project > Run
3. Delete and reload all referenced .dlls
4. Delete all .pdbs and .dlls from the bin and obj folder. Reload the .dlls > Recompile > Run
5. Close Visual Studio IDE and restart. Rebuild and Run. Surprisingly it works
6. Restart your computer. Rebuild and Run. I refer to this as the "Windows Magic"
7. Make sure that the XML Element "compilation" tag in your web.config file has an attribute with debug = "true". Only if this is enabled, web apps and services have their .pdb files generated with the .dlls

Another Tip

• While debugging in Visual Studio, click on Debug > Windows > Modules. The IDE will dock a Modules window, showing all the modules that have been loaded for your project.
• Look for your project's DLL, and check the Symbol Status for it.
• If it says Symbols Loaded, then you're golden. If it says something like Cannot find or open the PDB file, right-click on your module, select Load Symbols, and browse to the path of your PDB.

I've reached as far as this. There might be other ways to overcome this. If there are, drop in a comment below. I don't want developers to suffer their debugging process. That's the only way they can spy on every single variable and other declarations.

Happy coding!!

Database is in Transition. Try the Statement Later.

I was recently trying to take the Database Offline when I encountered this error :

Database is in Transition. Try the Statement Later.

How did I resolve this problem? I just re-started SQL Server Management Studio and the Database was accessible again.