tag:blogger.com,1999:blog-5976686513564131325.post7666953697864802346..comments2024-03-17T15:34:05.492-06:00Comments on MPECS Inc. Blog: CaseWare and SMB2 Update – Install A HotfixPhilip Elder Cluster MVPhttp://www.blogger.com/profile/06082028960643490292noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5976686513564131325.post-55491083224085212722011-10-27T11:21:23.421-06:002011-10-27T11:21:23.421-06:00For anyone who is interested: while MS has release...For anyone who is interested: while MS has released the hotfixes and while one is included in win2K8SvrR2 Service Pack 1, both hotfixes will not install on SBS 2011 even though the platform is based on win2K8SvrR2. the error message indicates "the update is not applicable to your computer"Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-15808542665325946212011-02-19T10:05:22.022-07:002011-02-19T10:05:22.022-07:00A.,
I am not an "expert", Expert, or an...A.,<br /><br />I am not an "expert", Expert, or anything else beyond someone that publishes their day to day experiences, along with contributions from others, on this blog.<br /><br />From the "About Me" on the blog:<br /><br />"Blog posts represent my opinion right or wrong, and should be taken as such."<br /><br />I make no claims to being infallible.<br /><br />As to the CaseWare situation with SMBv2, we have had a number of other product related issues. So, colour my glasses red, but it sure makes things difficult to _<i>not</i>_ pin the problems on the product itself.<br /><br />Now, as to an apology, yes, you may be right about the need for one, however, before that happens how about I throw the ball back your way.<br /><br />The <a href="http://support.microsoft.com/kb/2028965" rel="nofollow">KB 2028965 hotfix</a> mentions that it is for users that work on the same file together.<br /><br />All of our issues have been with either roll-forwards or when the user is populating a new CaseWare file with the client's info. CaseWare would just stop working. At no point was more than one user working on that file for any reason when the crashes happen in CaseWare.<br /><br />If the problem was purely SBM2, then CaseWare would stop functioning on _<i>all</i>_ files located on that network server. This does not happen.<br /><br />So, it is not so easy to wash responsibility for the problem away from the vendor.<br /><br />PhilipPhilip Elder Cluster MVPhttps://www.blogger.com/profile/06082028960643490292noreply@blogger.comtag:blogger.com,1999:blog-5976686513564131325.post-54805454115746874842011-02-19T00:19:13.554-07:002011-02-19T00:19:13.554-07:00To quote from your earlier blog post:
"Those ...To quote from your earlier blog post:<br />"Those that put Microsoft on the hook may need to take a step back as the software vendors may be the ones on the hook for this."<br /><br />Now that MS has admitted to YET ANOTHER major SMB2 bug, where's the apology to CaseWare and other innocent software vendors. <br /><br />They are victims of MS's bad testing and then to make it worse, IT "experts" like yourself make idiotic accusations. <br /><br />"We think that we are seeing legacy components failing to work with the new structures to be found in SMBv2". Really? That sentence doesn't even make sense. The move from SMB1 to SMB2 should have been INVISIBLE to application programs using the Win32 API. If SMB2 doesn't behave the same way as SMB1, IT IS A BUG in SMB2. Plain and simple.<br /><br />Can you produce any MS documentation that states application developers such as CaseWare should do ANYTHING different if their program is running on SMB2 vs SMB1? I don't think so.<br /><br />Just apologize to CaseWare on your blog. It's the right thing to do.Anonymousnoreply@blogger.com