lost this post some how … sorry.
To solve this follow the work around:
Work Arround 1:
- Start Menu, click Run, type > control admintools and then click OK.
- Double-click Local Security Policy.
- Click Software Restriction Policies.
Note: If no software restrictions are listed, right-click Software Restriction Policies, and then click Create New Policy.
- Under Object Type, double-click Enforcement.
- Click All users except Local Administrators, and then click OK.
- Restart the computer.
Install SP1 with no errors.
Work Arround 2:
There is a fix from Microsoft to resolve the issue. Please visit the following knowledge base article:
http://support.microsoft.com/kb/925336 or Download the Update for Windows Server 2003 (KB925336).
Note: Revert the settings after the installation is over.
In general whenever we need to get physical location of the file in ASP.Net Application, we use Server.MapPath. This is the most commonly adopted method. If you want the file to be located with reference to the path of the current WebPage, then the implementation holds good, but, in case you have to always refer the file from the application root, this method gives you different results. Take the following scenario, where the application directory structure is as follows:
- ClassA.cs (uses Server.MapPath(“\Data\Data.XML”))
- ClassB.cs (uses ClassA to get the XML file contents)
- ClassC.cs (uses ClassA to get the XML file contents)
In the above scenario the ClassC will fail to retrive the contents in case of the WebApplication is hosted in a virtual directory. The application will work fine if it is a website. So the implementation will not show any errors when we run the application from the Visual Studio. to make it more generic we can replace the Server.MapPath with
System.Web.Hosting.HostingEnvironment.ApplicationPhysicalPath + @”Data\Data.XML”.
Virtualization’s big push to fame was arguably kick-started by VMware’s Workstation product, which allowed individual users to run a bunch of OSes, versions or instances (similar to multiple application windows) instead of having a one-at-a-time multi-boot environment. In many companies, virtualization arrived with developers first using the technology quietly to do testing and development, then introducing the virtualization tools to IT higher-ups.
While today, computer virtualization fuels many production environments, e.g., servers, desktop infrastructures, and as a provisioning tool, virtualization is also used by a still-growing number of software developers. For starters, they use virtualization tools to provide a range of target environments for development and testing (such as different operating systems, OS versions and browsers), and also to provision/re-provision configuration instances quickly and easily.
Here’s a look at how and why some of today’s developers are using virtualization and what their quibbles are with the technology as it stands.
Provisioning Multiple Test Environments
Mark Friedman, a senior software architect, works in Microsoft’s Developer Division, where upwards of 3,000 people create Visual Studio and the .NET Framework. Friedman himself works mainly on the performance tools that ship with Microsoft’s Visual Studio Team System. “About two-thirds of the people in my division are in development and testing — and most of these developers and testers are using system virtualization (via Microsoft’s Hyper-V technology) as one of their key productivity tools,” says Friedman, who is also a board director of The Computer Measurement Group.