Service not found?!!

I've been working on a dry run of an upgrade of one of the web apps we use regularly at work and have run into a snag that I just can't seem to get past.  Hopefully I'll get past it tomorrow, thanks to a call that I plan to make to the software author's technical support department, but then again the problem I'm having is so "weird" that I'm not all that certain that it's going to be an easy fix.  What I'm stuck with, for now, is a "Service not found" when I attempt to access the website for the app (on my test system).  I've had the app working just fine there in the past, as in just a few days ago, using a demo installation.  It's the whole process of getting from that test/demo status to a test status where we'd be using a copy of the real data that we use on our "live" system.  The issue that is screwing with me, which started it all, was trying to perform an upgrade from our database on the older app to a database that would be used for the new app.

I fear that I may wind up having to blow away my test server and reload it from scratch, then perform a fresh installation of the application(s) that I'm working with as it seems that my issues are so mysterious in nature.

At least these issues are being caught and dealt with now, while I'm in the testing/prep stage.  I'd hate to have run into these issues during the actual upgrade, whenver that will take place.

1,569 views 2 replies
Reply #1 Top

That is why we need test servers.  Sometimes the best answer is a clean start.

Reply #2 Top

Going back to some basic troubleshooting found the source of my "Service Not Found" problem: Tomcat.  Tomcat had been used on the system for another program/web service/app.  Removing that app left things "dirty" and didn't actually remove the reference to Tomcat that had been inserted into the Web server (IIS).  Ugh.  The sad part is that I couldn't find a way to fix that issue short of blowing away my test server and reloading it from scratch.  Blech.

I loathe applications that don't clean up behind themselves.  Really loathe them.  It is really unexcusable that an app would do that to a system.

I'll be back in the office tomorrow playing with my test server working to get the app that I'm currently working on back into a testable state.  I've gotta get back to where I can upgrade the database that is used for the old version of the app and then use that upgraded db for the new version of the app.  That whole upgrade process is what was apparently failing before, so I really need the test system working like it should.

Oh well, at least I'll get to take time off on Thursday without having to use any of my paid-time-off (swapping my Sunday for Thursday). :D