Gang Aft Agley

I was notified today that a module that I had written was not currently working. We had just finished testing some new functionality a month ago and now everything was broken. It was in our Document Directory module. Users are allowed to create folders and upload files to them, relating these documents to other pages within their website. Paul was writing new documentation, to coincide with the new design, when he discovered that renaming a folder caused all of the files inside it to be lost. A bit of digging into the specifics showed us that upon renaming the folder, in the database the name was changed from ‘documents/x’ to ‘Documents/y’, not a big change, but when you are doing text comparison ‘d’ and ‘D’ are not the same.

Asking around I found out that the servers had definitely had a patch installed on them in the days between nov 12th and dec. 23rd. I put the blame on this bug squarely on the patch, just because windows is case insensitive in its directory structure, it doesnt mean everyone is using it in a case insensitive manner.

Status at the end of the week. It doesnt seem to be the coding that is causing the problem. Upgraded versions of the MDAC components and the connection still fails, though it doesnt hang up the machine when it does. Now we are looking at Networking issues. Only problem with that is I suggested that 4 weeks ago as the problem, and I was told it had to be an error in the code that I didn’t write but must maintain. In the meantime I have learned how to use a wide array of performance monitoring tools, and spent a long time reading log files looking for patterns in the occurrrences. I have now sent the network monitorring files off to microsoft. End of week status same as last week, we know a little more about what is not causing it but dont know what is.

We are having a problem at work causing one server to hang occasionally. after several weeks of not being able to pinpoint exactly what was causingt this problem we broke down and called microsoft. After 1 hour on the phone we had updated our mdac components to 2.7 from 2.6 and were promised a link in an email for information on settng up the debugger for analyzing the problem. After receiving the email I clicked on the link and ended up at this page

The Knowledge Base (KB) Article You Requested Is Currently Not Available

To think we spent an hour on the phone to find out that they don’t know where on their website they have any information. I tryed searching for both the article id and for the title as well as keywords and struck out. We finally found the information we assume we want on a third party site, with links back to microsofts tools that work. So we have the debugger installed and are all ready to go, if it will hang up for us again.