My Monday morning WTF comes from IIS7 on Windows 7. I recently installed Coldfusion9 on this machine which has a handful of existing ASP.NET 3.5 web applications. The problem I ran into came after installing Coldfusion9 and electing to configure all IIS websites to work with CF. While that is convenient, it ended up breaking one of my ASP.NET applications that was using ASP Validation controls on a login form. Now that things are figured out, here are the details.
Firing up my ASP.NET application gives me the error message :
The WebResource.axd handler must be registered in the configuration to process this request
WebResource.axd handler must be registered
Obviously all I could think is WTF?!?!? since this application worked on Friday and now it is broken. The first thing I want to point out is that in my situation, the suggested solution of mapping WebResource.axd in the httpHandlers section of my web.config did not help this problem. After some googling I cam across this post on the IIS.NET forums which put me on the right track. You can read the details there if you want a good background on MS’ response and other users running CF and ASP.NET on the same box.
I’m happy to say I have three workarounds for this issue. Hopefully these will help you as well.
1. Change your AppPool to run in Classic Mode
- In inetmgr, put your web application into it’s own Application Pool ( unless it’s already in it’s own pool )
- Change that AppPool’s Managed pipeline mode to “Classic”
- You should be good to go
Classic mode is for compatibility ( think IIS6 )
2. Stop using ASP Validation controls
All ASP.NET Validation controls are hosted by WebResource.axd. If you stop using ASP Validator controls, the server will stop asking for WebResource.axd.
Removing ASP Validator controls should remove this error
3. Remove Coldfusion handler mappings from your ASP.NET site
If your ASP.NET app isn’t using Coldfusion, I would suggest doing this as your solution. Even if you do need Coldfusion in your ASP.NET app, you could still host your CF app in it’s own Virtual Directory and request if via ASP.NET.
- Open inetmgr
- Select your web app on the left ( under Default Web Site )
- In Features View on the right, double click Handler Mappings
- Sort your Handler Mappings by Name, and remove all entries titled “AboMapperCustom-*”
- Now your ASP.NET should work like a champ.
IIS7 Handler Mappings
Coldfusion9 Handler Mappings
Monday WTF solved. Now to get back to pushing buttons.
Tags: asp.net, coldfusion, iis7, inetmgr, web.config, webresource.axd
Posted in .net, adobe, coldfusion, development, microsoft, tips and tricks, windows | No Comments »
EDIT :
After finishing this post I ran into all sorts of other strange issues and restarted using a Web Appliction instead of a plain old Website. Between IntelliSense not showing any classes, to project reference issues, I couldn’t figured it out in time. I’m sure there’s a way, I just had to move on. So maybe this ramble below will be helpful for someone.
EF
Just ran into something quirky with Visual Studio 2008’s new ADO.NET Entity Data Model wizard. While working on an ASP.NET 3.5 website ( not a codebehind web application ) I was trying to get the ADO.NET Entity Data model wizard to work with MySQL and ran into a probable Visual Studio bug. To sum up the issue, if you are going to add a new edmx to your project, do NOT save it to the App_Code folder initially. Put it in your root folder, compile your project, then move the edmx where you’d like.
Assuming you’ve already created your ASP.NET Website project, here’s how you reproduce this issue.
Right click your project and left click ‘Add New Item’
Add New Item
Select ADO.NET Entity Data Model, name it, select your language of preference
ADO.NET Entity Data Model
Click Yes to the ‘Store in App_Code’ prompt
Place file in 'App_Code' folder
Complete the new Entity Data Model wizard
See this tutorial if you have not done this before
Compile project after completing wizard
Invalid token 'void' in class, struct, or interface member declaration
At this point your project should have a new.edmx file located inside of the App_Code folder, but the project won’t build without failing. If you are stuck in this predicament, follow this workaround.
Move .edmx to root folder and rebuild
WORKAROUND : move edmx to root folder, then recompile
After moving your edmx file to the root folder you should be able to compile without problem. Assuming this solves your problem, you should be able to move your edmx file to the App_Code folder without problem. Seems like an initial compile problem.
Tags: ADO.NET, ADO.NET Entity Data Model, edmx, error, mysql, Visual Studio, visual studio 2008, void
Posted in .net, C#, Visual Studio, development, hack, microsoft, mysql, tips and tricks, windows | 2 Comments »
I do a lot of moving of databases between development and production servers. If I’m lucky, the production server I’m working with gives me access to DTS services, or even the Database publishing wizard. More often than not however, the SQLServer I’m pushing to is locked down in a way that I am required to Remote Desktop into the server, then update the database via restore.
So here’s the tip. When you’re only means of updating a remote SQLServer database is by physically restoring the database, do your best to mirror the product server’s database location on your development machine. Check out this screenshot, and you’ll see what I mean
MSSQL : Restore Files and Filegroups
The background of this image shows that my production server houses all of it’s databases at the path C:\DB\database.mdf.
The lower right box shows where I keep my databases on my development server. Since I do not store any vital data on my C: drive, I’ve changed the path to D:\DB.
While this isn’t an exact path match, this trick saves me a little bit of time and frustration when restoring a database remotely. Especially when I have to do it more than a handful of times in the same day.
It’s assumed you know how to the following :
- Back up a SQLServer database
- Copy the BAK file to a remote server
- Connect remotely to your SQLServer
- Restore a Database file from a file ( BAK file )
Tags: bak, mssql, paths, restore database
Posted in database, microsoft, sql, tips and tricks, windows | No Comments »
Yesterday morning I started work as usual as ran into a problem mounting one of the shares from my XP PRO machine on my Macbook Pro. Obviously the first question I asked was WTF? Everything worked yesterday, and not today.
I did some Googling and found mention about opening some UDP ports, but my TCP/IP settings currently has all ports open, so that didn’t help. Then just for giggles I decided to turn off simple file sharing. That fixed it!
So if you receive the message “A volume failed to mount”, and then another one with “Error code -6602″ in it, you should check your PC’s file sharing settings. You would do this by following these steps.
How to disable simple file sharing on XP
- Open Windows Explorer ( Win+E or double click My Computer )
- Click Tools > Folder Options
- Click the View Tab
- Scroll down to the bottom, and uncheck “Use simple file sharing (Recommended)”
- Then retry mounting the share on OSX
-
-
-
The operation could not be completed. ( Error code -6602 )
-
Tags: -6602, file sharing, mount, osx, osx error code, osx to pc networking, pc, shared folder, simple file sharing, volume, xp
Posted in apple, microsoft, osx, tips and tricks, windows | 2 Comments »
