Production Chaos
-
We "prestaged" a .NET 2.0 web service on a production server a while ago, it was working correctly at the time. Today the service is supposed to be used and it is not working. What I found out is, application pools are not set up properly on the server, the .NET 2.0 web service is in the same pool with other .NET 1.1 applications. Finding out this is not easy since I don't have access to the server and the admins (of this server) are not familiar with ASP.NET at all. I told the admins how ot fix it: creat a new app pool for the .NET 2.0 web service. Later I was told the web service was working without my suggested change. It turns out, someone reset IIS and the .NET 2.0 web service was loaded before .NET 1.1 apps. Of course this makes all .NET 1.1 applicatoins in the same pool not working. My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it. :doh:
My .NET Business Application Framework My Younger Son & His "PET"
-
We "prestaged" a .NET 2.0 web service on a production server a while ago, it was working correctly at the time. Today the service is supposed to be used and it is not working. What I found out is, application pools are not set up properly on the server, the .NET 2.0 web service is in the same pool with other .NET 1.1 applications. Finding out this is not easy since I don't have access to the server and the admins (of this server) are not familiar with ASP.NET at all. I told the admins how ot fix it: creat a new app pool for the .NET 2.0 web service. Later I was told the web service was working without my suggested change. It turns out, someone reset IIS and the .NET 2.0 web service was loaded before .NET 1.1 apps. Of course this makes all .NET 1.1 applicatoins in the same pool not working. My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it. :doh:
My .NET Business Application Framework My Younger Son & His "PET"
-
Makes me feel happy that I'm still working on Client/Server where I have full control.
Two heads are better than one.
Norm .net wrote:
Makes me feel happy that I'm still working on Client/Server where I have full control.
Until the next Windows update, at least :rolleyes:
Agh! Reality! My Archnemesis![^]
| FoldWithUs! | sighist | µLaunch - program launcher for server core and hyper-v server. -
Makes me feel happy that I'm still working on Client/Server where I have full control.
Two heads are better than one.
Well but it's the same as wanting to run two assemblies, one 1.1 and one 2.0, in the same .NET AppDomain. It just won't work. Or, rather, it works, but only for dependencies (IIRC).
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe, but not a personality. [Charlie Brooker] ScrewTurn Wiki, Continuous Localization and My Startup
-
We "prestaged" a .NET 2.0 web service on a production server a while ago, it was working correctly at the time. Today the service is supposed to be used and it is not working. What I found out is, application pools are not set up properly on the server, the .NET 2.0 web service is in the same pool with other .NET 1.1 applications. Finding out this is not easy since I don't have access to the server and the admins (of this server) are not familiar with ASP.NET at all. I told the admins how ot fix it: creat a new app pool for the .NET 2.0 web service. Later I was told the web service was working without my suggested change. It turns out, someone reset IIS and the .NET 2.0 web service was loaded before .NET 1.1 apps. Of course this makes all .NET 1.1 applicatoins in the same pool not working. My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it. :doh:
My .NET Business Application Framework My Younger Son & His "PET"
Xiangyang Liu 刘向阳 wrote:
My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it.
Welcome to the world of production support! I have had these kind of mornings and nights several times in my career. Also no matter how much careful you can't prevent such a situation. Debugging and troubleshooting in production environments is a skill that no body can claim to have mastered especially when it comes to dealing with people. Every time I am forced in such a situation, I learn something new. I was thinking of writing case study articles on debugging and troubleshooting in production environments. May be one day!
-
We "prestaged" a .NET 2.0 web service on a production server a while ago, it was working correctly at the time. Today the service is supposed to be used and it is not working. What I found out is, application pools are not set up properly on the server, the .NET 2.0 web service is in the same pool with other .NET 1.1 applications. Finding out this is not easy since I don't have access to the server and the admins (of this server) are not familiar with ASP.NET at all. I told the admins how ot fix it: creat a new app pool for the .NET 2.0 web service. Later I was told the web service was working without my suggested change. It turns out, someone reset IIS and the .NET 2.0 web service was loaded before .NET 1.1 apps. Of course this makes all .NET 1.1 applicatoins in the same pool not working. My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it. :doh:
My .NET Business Application Framework My Younger Son & His "PET"
You just touched on a fundamental (but often ignored) concept of software development: working does not mean the same thing as correct.
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFiles -
You just touched on a fundamental (but often ignored) concept of software development: working does not mean the same thing as correct.
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesYes reminds me of this: http://www.buildsonmymachine.com/[^]
-
Xiangyang Liu 刘向阳 wrote:
My whole morning (since 6am) was spent explaining to people why it is working / not working and how to fix / not fix it.
Welcome to the world of production support! I have had these kind of mornings and nights several times in my career. Also no matter how much careful you can't prevent such a situation. Debugging and troubleshooting in production environments is a skill that no body can claim to have mastered especially when it comes to dealing with people. Every time I am forced in such a situation, I learn something new. I was thinking of writing case study articles on debugging and troubleshooting in production environments. May be one day!
It got worse... Now that everyone is convinced what is causing the problem and how it should be fixed, nobody wants to do it. It takes a total of 30 seconds to do it (the actual down time will be less). But since the server is managed by a different team (under a different division with different VP), we need to get top level approval on the ground that it may affect production users. Also we cannot do it outside the 12am - 6am window. It is already affecting production users for god's sake (several .NET 1.1 applications stopped working).
My .NET Business Application Framework&nsbp; My Younger Son & His "PET"
-
It got worse... Now that everyone is convinced what is causing the problem and how it should be fixed, nobody wants to do it. It takes a total of 30 seconds to do it (the actual down time will be less). But since the server is managed by a different team (under a different division with different VP), we need to get top level approval on the ground that it may affect production users. Also we cannot do it outside the 12am - 6am window. It is already affecting production users for god's sake (several .NET 1.1 applications stopped working).
My .NET Business Application Framework&nsbp; My Younger Son & His "PET"
One word: deploy on the Cloud
-
You just touched on a fundamental (but often ignored) concept of software development: working does not mean the same thing as correct.
-=- James
Please rate this message - let me know if I helped or not! * * *If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong!
Remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road!
See DeleteFXPFilesJames R. Twine wrote:
working does not mean the same thing as correct.
But working is more convenient than correct to most people including developers. :)
My .NET Business Application Framework&nsbp; My Younger Son & His "PET"
-
One word: deploy on the Cloud
Four words: What is the cloud? :-D
My .NET Business Application Framework&nsbp; My Younger Son & His "PET"
-
Four words: What is the cloud? :-D
My .NET Business Application Framework&nsbp; My Younger Son & His "PET"
