|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
KB913384Is there anyone that can give me more info on KB913384? I've found a
dotnet2 hotfix1 on the web and its our exact problem, but we won't install until we know its legit and more about what it was originally created for... [Patch Attributes] PatchCode={DC18570F-307A-4ECA-BBF8-CC025CF6C483} ID=KB913384 Uninstallable=1 [Wrapper Config] PatchTitle=NDP20-KB913384-X86 KBArticle=913384 http://www.builderdash.com/DotNet2.0_hotfix1.exe Changes the framework to 2.50727.63 ... Thx So I take it this is a super secret hotfix that no one should have
knowledge about : ) I have read KB913384...
and personally downloaded the fix from... http://www.builderdash.com/DotNet2.0_hotfix1.exe the only thing that Microsoft has on it at this time is... http://support.microsoft.com/default.aspx?scid=kb;en-us;913384&sd=rss&sp id=8291 Interestingly enough, they do not provide a download link only a contact url for this problem at: http://support.microsoft.com/contactus/?ws=support I had this problem with IIS6 and Windows Server 2003, latest patches etc; as soon as I started setting up ASP.NET 2.0/.NET Framework 2.0 applications, when the Visual Studio 2005 RTM was released in November 2005... This hot fix did in fact solve my problem... I guess Microsoft does not want it to be common knowledge that they put out their flagship product(s) with access violations that occur in very common deployment configurations. *** Sent via Developersdex http://www.developersdex.com *** LvBohemian wrote:
> I have read KB913384... I suppose you didn't bother trying to contact product support to see what it > > and personally downloaded the fix from... > http://www.builderdash.com/DotNet2.0_hotfix1.exe takes to get a hotfix. When I've gone through the process it took less than 15 minutes and was done entirely by email. Someone from product support even followed up a few days later to make sure the hotfix solved my problem (which it did). As is, you installed an executable that you got from a 3rd party that may or may not actually contain (just) the official hotfix - I hope you really trust builderdash.com - whoever that is. I wouldn't. > I guess Microsoft does not want it to be common knowledge that they ....or maybe they just followed their standard practice for hotfixes - write > put out their flagship product(s) with access violations that occur > in very common deployment configurations. a knowledge base article and make the hotfix available for those who need it. Hotifxes are generally subject to only limited testing and frequently have interdependencies that require management (e.g. there may be two hotfixes for problem B depending on whether you've already go the hotfix for problem A). Hotfixes are the primary component of service packs, at which time they get fully tested and broadly deployed. -cd Thank you for your response and opinion...
I did in fact verify that the download at http://www.builderdash.com/DotNet2.0_hotfix1.exe Was valid for KB913384 and that in my opinion Microsoft Product Consumers would be better served by Supplying a link to directly download hot fix, instead of another layer and subsequent delay in determining if this will resolve issue or not. It’s been my experience (including but not limited to KB913384) that in contacting Microsoft Product Support Services it is seldom responded to instantly... Which when trying to resolve something like this; is needed. In my opinion, if an individual wants to test a hot fix, let them do so at their own risk; if they have one already available that may or may not solve the problem; give them a direct link for instant gratification. Obviously the testing of such a hot fix would be on a development test server for testing service packs, hot fixes etc… In the time it took MSPSS to respond to KB913384, in my case I could have totally re-installed the o/s on the server and several others and reinstalled all web apps, services etc... It took them Days, not minutes to respond... Which considering the number I MS product users, I do not find extreme; so I reiterate if they have a possible fix; make it available for instant gratification/validation etc. Best Regards, LvBohemian [MAS, BAS, MCAD, MCSD, MCSE, MCDBA, et. al.] *** Sent via Developersdex http://www.developersdex.com *** Really - I contactes PSS after the third VB compiler crash that routed me to
the technet article about a supported hotfix. In less than 30 minutes, I had the hotfix for not only that particular problem, but also for the framework IDE performance issue, which I hadn't even run across. Downloading a MS hotfix from other than a site MS given you by PSS is simply dangerous. Mike Ober. Show quote "LvBohemian" <nospam@devdex.com> wrote in message news:O5ewmW0gGHA.1208@TK2MSFTNGP02.phx.gbl... > Thank you for your response and opinion... > > I did in fact verify that the download at > http://www.builderdash.com/DotNet2.0_hotfix1.exe > Was valid for KB913384 and that in my opinion Microsoft Product > Consumers would be better served by > Supplying a link to directly download hot fix, instead of another layer > and subsequent delay in determining if this will resolve issue or not. > It's been my experience (including but not limited to KB913384) that in > contacting Microsoft Product Support Services it is seldom responded to > instantly... > Which when trying to resolve something like this; is needed. In my > opinion, if an individual wants to test a hot fix, let them do so at > their own risk; if they have one already available that may or may not > solve the problem; give them a direct link for instant gratification. > Obviously the testing of such a hot fix would be on a development test > server for testing service packs, hot fixes etc. > > In the time it took MSPSS to respond to KB913384, in my case I could > have totally re-installed the o/s on the server and several others and > reinstalled all web apps, services etc... > > It took them Days, not minutes to respond... > Which considering the number I MS product users, I do not find extreme; > so I reiterate if they have a possible fix; make it available for > instant gratification/validation etc. > > Best Regards, > LvBohemian > [MAS, BAS, MCAD, MCSD, MCSE, MCDBA, et. al.] > > > *** Sent via Developersdex http://www.developersdex.com *** >  |
|||||||||||||||||||||||
Other interesting topics