Archive

Archive for the ‘Windows’ Category

How to Install SQL Server Management Studio 2005 on Vista 64-bit

March 22nd, 2010 2 comments

If you have tried to install the 64-bit version of SQL Server Management Studio on Vista 64-bit, then you have probably run into the following error:

Product: Microsoft SQL Server Management Studio Express — The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 29506.

The problem is that User Access Controls (UAC) interferes with the installation process and causes it to fail. In order to get around the UAC issue, follow these few simple steps:

  1. Save the SQL Server Management Studio MSI file to, say, “C:\temp”
  2. Go to Start > All Programs > Accessories
  3. Right-click on “Command Prompt”, and click “Run as Administrator”
  4. Once you open the command prompt, browse to “C:\temp”
  5. Run the MSI file by typing in the name of the file and hitting Enter

The installation will run using the administrator privileges inherited by the command prompt.

You should now be free of any error code 29506. Good luck!

Improve Scalability and Performance in ASP.NET Apps

March 17th, 2009 No comments

If you’re looking to scale out ASP.NET applications, here is an interesting article that goes into length on important aspects to improve performance for .NET applications in high-traffic environments.

    The article covers the following topics:

  • Optimizing the ASP.NET pipeline system
  • ASP.NET, AJAX caching, and what you need to know
  • Deploying ASP.NET from a staging to a production environment
  • Optimizing the ASP.NET process configuration
  • Using a Content Delivery Network (CDN) with your ASP.NET apps
  • ASP.NET 2.0 Membership tables
  • Progressive UI loading for a smoother, end-user, browser experience
  • Optimizing ASP.NET 2.0 Profile provider

Original article: Performance & Scalability in ASP.NET

Cloud Hosting – Scaling Websites the Easy Way

February 2nd, 2009 No comments

One often has to make a choice when it comes to website hosting. You weigh the variables and decide on the best solution for your hosting needs. Cloud hosting makes this decision a WHOLE lot easier. Let’s break it down.

Price. You want to get the best deal possible. Shared hosting probably comes to mind first. In the classic sense, shared hosting means a company has a server, and they load as many websites onto this server in order to make the most profit from one server. Sometimes, this can mean hundreds of websites on one box. One box… susceptible to the same physical hardware limitations as any other server. Sure, they might even include RAID, redundant power supplies, and a lot of disk space.

However, what happens when your website actually starts getting traffic? I had an experience where my company put their trust in a shared hosting company (*cough* Dreamhost *cough*). When it came down to it, one of our websites had a lot of visitors one evening, and after battling to keep things running smoothly, the host ultimately disabled our website via renaming the index file to index.php_disabled_by_host. Seriously? So much for saving money and “unlimited” space and bandwidth… which brings me to my next point.

Scalability. If you have a website that has outgrown shared hosting, what is your next move? Many people consider purchasing dedicated equipment for their website. A dedicated server is usually the first move. Not enough? Scaling out from this point then usually requires the purchase of another dedicated server and a load balancer, then it just gets pricier from there with a dedicated database server, file servers, caching servers, and more to handle growing traffic and load. We’re talking a significant amount of expenses just to get the ability to scale.

Scale My Site is the answer. The concept of a cloud host is that it takes the best of the scalable, dedicated world and lets you just pay for what you use. You put your website in the cloud and instantly your application is scaled across multiple webservers. Your files are stored on a redundant SAN mirrored across many physical drives. Database queries are performed on powerful, multi-node database clusters. You don’t have to think about “how am I going to handle all of that traffic?” because it just happens automatically. You no longer have to think about “do I need a Windows or Linux based account?”. It doesn’t matter. You can run ASP.NET applications side-by-side PHP web sites. It’s the cloud that doesn’t mind – it’s cool with whatever you want to do. I highly recommend checking out Ninja Systems, the cloud hosting company, if you are serious about scaling your website, and if you don’t want to waste your time recreating another scalable infrastructure that you need to manage yourself.

Run ASP.NET on Non-Standard Page Extensions

September 26th, 2007 No comments

If you have ever wanted to convert an existing HTML-based website to an ASP.NET website, but you didn’t like the idea of losing the “page rank” of those pages, I have the solution. Recently, a friend asked for help on this subject, and since we couldn’t find sufficient information online, I am putting the steps to do this in my blog. In this first case, we wanted to use ASP.NET on long-standing pages that had .html and .htm extensions, but this can apply to all other extensions.

Setup ISAPI Application Mapping

The first step is to tell IIS what system you would like the extension to map to.

  1. Open your existing website in IIS
  2. Browse to the Home Directory tab
  3. Open the Application Settings Configuration (you should see a list of existing application mappings)
  4. Click “Add”
  5. Browse for the .NET Framework you want to use (e.g.: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll)
  6. Enter the extension (such as .htm)
  7. Limit the mapping to specific verbs (e.g. GET,HEAD,POST,DEBUG)
  8. Check Script Engine
  9. Uncheck Check that File Exists
  10. Click OK and close IIS

Note: If you trouble with a greyed out OK box, check out this KB article: http://support.microsoft.com/?id=317948

Update Web.Config with HttpHandlers and BuildProviders

The last step is to update the Web.config for your website so that ASP.NET knows how you want to manage these new extensions. You will first need to add in a new HttpHandler inside of the System.Web node:

<httpHandlers>
<add verb=”*” path=”*.htm” type=”System.Web.UI.PageHandlerFactory”/>
</httpHandlers>

Finally, we will need to add a buildProvider:

<buildProviders>
<add extension=”.htm” type=”System.Web.Compilation.PageBuildProvider”/>
</buildProviders>

Now save the Web.config file and run your ASP.NET -powered, non-standard-extension page!

For more information on BuildProviders, click here

Good luck!

Matt Beckman

Categories: ASP.NET, General, Web Servers, Windows Tags: , , ,