Abhishek Bhowmick | SharePoint Blog

Unable to connect the Virtual PCs to the internet in Windows Server 2003

Posted in Virtual PC by Abhishek Bhowmick on November 30, 2008

This is a common situation we all virtual techies face when we use Microsoft’s Virtual PC when we need to the internet traffic from the host system to your virtual machines.  There is this blog which gives us a clear explanation what happens and how does it work under the hood (Link to the source blog mentioned below).

Normally using Shared Networking is very simple.  You just enable it and set the guest operating system to use DHCP – and everything works.  This is not the case with a Windows Server 2003 guest though.  The problem is that Shared Networking configures the guest operating system to use the same DNS servers as are used by the physical computer.  However – all DNS packets are actually returned from ‘192.168.131.254’ – which is the virtual gateway used by Shared Networking.  Windows Server 2003 looks at the DNS packet, sees that it is coming from a source other than the DNS server it requested the information from, and rejects it.  A simple fix for this is to manually assign the DNS server inside the virtual machine to 192.168.131.254 – then everything will work just fine.

Source: http://blogs.msdn.com/virtual_pc_guy/archive/2005/01/06/347965.aspx

Advertisements

Unable to save .pdf files to Sharepoint document library

Posted in Sharepoint by Abhishek Bhowmick on November 20, 2008

Unable to save .pdf files from Adobe Acrobat Reader to the Sharepoint Document Library.  As per http://support.microsoft.com/kb/265867/en-us this is a known issue and the workaround is mentioned in the Microsoft KB article.  During troubleshooting it is discovered there is another way this can be done.

For this we first need to ensure that WebDav is enabled in Web Service Extensions in the IIS.  Also make sure that the WebClient service is running in the Services.msc in Windows Server 2003.  Once we have this done, we add a network place using the UNC path.  For instance, if your document library url is http://sharepoint/documents then type in the path as \\sharepoint\documents and this would ask for your valid credentials.  Once you enter your credentials, a network share folder would be created in your My Network Places.  Now you can open your favorite .pdf files in the Adobe Acrobar Reader and save a copy of it directly into the Sharepoint Document Library using the netwrok share in My Network Places.

Note:  The above procedure can be used only to create network shares for folder in the Sharepoint site running on port 80 only.  This is because Web Folders are created for other port numbers and as per the above quoted Microsoft KB article, it is a known issue that .pdf files cannot be saved.  This applies to all non Office applications like .jpg, .rtf etc…

Run Internet Information Services (IIS) in 32 bit emulation mode

Posted in Sharepoint, Windows by Abhishek Bhowmick on September 30, 2008

If you are running Windows Server 2003 x64 based operating system and you are installing x86 based application which would need to run on Internet Information Services (IIS) then you must run IIS in 32 bit emulation mode.  To do this follow the steps below:

• Click Start, and then click Run.
• In the Open box, type cmd, and then click OK.
• In the command prompt window, navigate to the %drive%:\Inetpub\Adminscripts folder, where %drive% is the drive in which Windows Server 2003 is installed.
• In the Adminscripts folder, type the following command:
cscript adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1

Note: The value “1” for Enable32bitAppOnWin64 specifies 32-bit mode, whereas the value “0” specifies 64-bit mode.

• Press ENTER.
• Type iisreset and then press ENTER.
• Close the command prompt window.

IIS would now run in 32 bit emulation mode and you can now install x86 based applications on the server.

%d bloggers like this: