Microsoft aren't the only ones with bugs!
Category None
Bookmark :
Sometimes when we've finally got to the bottom of a customer's problem, it is clear that someone else's software is to blame. Of course, this is of little interest to the customer who just wants a working system, and so we then set to work finding a work-around to fix their problem. These bugs aren't always in Microsoft's software (although they have their own share of "undocumented features"). With Microsoft, most of our problems are down to bad or incorrect documentation.
However we had a couple of new issues to fix recently that highlighted how obscure other people's problems can be. In one case Novell's NetWare was causing us problems when looking at files on netware filesystems that were hidden --- for reasons known only to Novell such files did not give up their ownership data as easily as they should and were appearing in SPACEWatch as owner "not known". We had to change the way we got this data and if you upgrade to v5.7.69 you'll get the fix.
In another example the customer was using MySQL on linux - but linux was running on an IBM mainframe. We support MySQL and SQL Server for use with SPACEWatch and normally this doesn't present too many problems. Of course they both have different ideas about what constitutes "SQL" - but we're used to that. In this case it was an undocumented "feature" of MySQL that had us scratching our heads for a long time. With the help of IBM we finally managed to isolate and reproduce the problem. So if you are running SPACEWatch and storing your space data in MySQL on a linux mainframe partition - you need v5.7.69!
Finally, and just to prove that our development and support engineers do talk to each other, as part of the MySQL issue I mentioned above we were able to re-engineer part of the database management. This means that all SPACEWatch users can experience up to 50% faster data merge operations - particularly when you're adding data associated with a whole new directory tree of data.
Bookmark :
Sometimes when we've finally got to the bottom of a customer's problem, it is clear that someone else's software is to blame. Of course, this is of little interest to the customer who just wants a working system, and so we then set to work finding a work-around to fix their problem. These bugs aren't always in Microsoft's software (although they have their own share of "undocumented features"). With Microsoft, most of our problems are down to bad or incorrect documentation.
However we had a couple of new issues to fix recently that highlighted how obscure other people's problems can be. In one case Novell's NetWare was causing us problems when looking at files on netware filesystems that were hidden --- for reasons known only to Novell such files did not give up their ownership data as easily as they should and were appearing in SPACEWatch as owner "not known". We had to change the way we got this data and if you upgrade to v5.7.69 you'll get the fix.
In another example the customer was using MySQL on linux - but linux was running on an IBM mainframe. We support MySQL and SQL Server for use with SPACEWatch and normally this doesn't present too many problems. Of course they both have different ideas about what constitutes "SQL" - but we're used to that. In this case it was an undocumented "feature" of MySQL that had us scratching our heads for a long time. With the help of IBM we finally managed to isolate and reproduce the problem. So if you are running SPACEWatch and storing your space data in MySQL on a linux mainframe partition - you need v5.7.69!
Finally, and just to prove that our development and support engineers do talk to each other, as part of the MySQL issue I mentioned above we were able to re-engineer part of the database management. This means that all SPACEWatch users can experience up to 50% faster data merge operations - particularly when you're adding data associated with a whole new directory tree of data.
