I am running Windows 2003 Server with an IIS application developed in VS 2003 (.NET Framework 1.1). The code is written in VB.Net and ASP.Net.
Last night my server updated itself normally. The majority of my application is working fine, components are instantiated and calls made to SQL Server as designed. However, links on the summary page point to pdf documents on a shared folder. These links error out now and the default error page designated in the webconfig file is returned.
The share is working correctly and I can load documents directly from the share. Also, the permissions on this share are correct.
The code behind component does 2 things that are not done in any other code in this application:
1) I use Request.Querystring(). (I do not see how this could be the problem.) 2) I use the following code fragment to write the pdf document to the calling page: Response.ContentType = "Application/pdf" Response.WriteFile(FilePath) Response.End()
I first removed Update #873333, which was also installed at the same time. After the reboot the application did not work.
I then removed Update #885250 (the process informed me that Update #890047 may not run correctly afterward). After the reboot, the application works fine.
I have a current support request in to the ASP.Net Group.
Are there any other developers out there encountering this particular problem?
Similar problem here. We have several Snap servers. After 885250 was applied to the workstations, they could access the shares on the snap servers, but could not create, modify, or delete any files or folders. Removing 885250 put things back to normal. This update modified the way SMB packets are validated. MS needs to go back to the drawing board on this one.
"Grant" wrote: > I am running Windows 2003 Server with an IIS application developed in VS 2003 > (.NET Framework 1.1). The code is written in VB.Net and ASP.Net.
> Last night my server updated itself normally. The majority of my application > is working fine, components are instantiated and calls made to SQL Server as > designed. However, links on the summary page point to pdf documents on a > shared folder. These links error out now and the default error page > designated in the webconfig file is returned.
> The share is working correctly and I can load documents directly from the > share. Also, the permissions on this share are correct.
> The code behind component does 2 things that are not done in any other code > in this application:
> 1) I use Request.Querystring(). (I do not see how this could be the problem.) > 2) I use the following code fragment to write the pdf document to the > calling page: > Response.ContentType = "Application/pdf" > Response.WriteFile(FilePath) > Response.End()
> I first removed Update #873333, which was also installed at the same time. > After the reboot the application did not work.
> I then removed Update #885250 (the process informed me that Update #890047 > may not run correctly afterward). After the reboot, the application works > fine.
> I have a current support request in to the ASP.Net Group.
> Are there any other developers out there encountering this particular problem?
"Jon" wrote: > Similar problem here. We have several Snap servers. After 885250 was applied
The pdf files that I have are on a Dell 705N, aka Snap 4100, NAS server (RAID 5) on which the directory of pdf files has been shared to the IIS application.
So, obviously then the code does not matter and the method I used to access and deliver the pdf to the client is not and cannot be the problem. Good! Now I don't feel so bad about starting the support call... I always worry when it can cost money. :)
Thanks for making me feel better about the problem, now if I can just get the thing solved without having to disable MS Update I will be a happy camper.
I'm also having trouble with this update. "Random" files through admin shares no longer appear in explorer. When copying folders from one computer to another, some files will not be copied (ie. 70 of 75 files make it).
If I try to create the same file (even though I cannot see it), it won't allow me because it says the file is already there (like it should), but it just doesn't "see" the file(s) anymore...
Same here. I've contacted Snap concerning this. They say that Microsfsoft changed the SMB code. They are hoping that Microsoft will pull the update until a proper solution can be resolved. I've seen it on XP SP1 and Windows Server 2003. It not only affects Snap servers but it also affect users that do not have the update when the server does and vice versa.
> > Similar problem here. We have several Snap servers. After 885250 was applied
> The pdf files that I have are on a Dell 705N, aka Snap 4100, NAS server > (RAID 5) on which the directory of pdf files has been shared to the IIS > application.
> So, obviously then the code does not matter and the method I used to access > and deliver the pdf to the client is not and cannot be the problem. Good! Now > I don't feel so bad about starting the support call... I always worry when it > can cost money. :)
> Thanks for making me feel better about the problem, now if I can just get > the thing solved without having to disable MS Update I will be a happy camper.
We are exhibiting the same problems. We have several SNAP servers that we can no longer access running Windows XP SP1a with patch 885250 installed. We can map the shared areas, but cannot access the data. If we uninstall 885250 everything works fine. Also, accessing the SNAP servers with 885250 and Windows XP SP2 works fine.
> > Similar problem here. We have several Snap servers. After 885250 was applied
> The pdf files that I have are on a Dell 705N, aka Snap 4100, NAS server > (RAID 5) on which the directory of pdf files has been shared to the IIS > application.
> So, obviously then the code does not matter and the method I used to access > and deliver the pdf to the client is not and cannot be the problem. Good! Now > I don't feel so bad about starting the support call... I always worry when it > can cost money. :)
> Thanks for making me feel better about the problem, now if I can just get > the thing solved without having to disable MS Update I will be a happy camper.
I can confirm this behaviour on Windows 2003 Servers accessing SNAP (smb) shares. I tested this with 3 brand new installed Windows 2003 Servers with all hotfixes applied. Removing KB885250 solved this issue. Guess I will not be installing this hotfix on a Windows 2003 Server.
"grim...@xs4all.nl" wrote: > I can confirm this behaviour on Windows 2003 Servers accessing SNAP > (smb) shares. > I tested this with 3 brand new installed Windows 2003 Servers with all > hotfixes applied. > Removing KB885250 solved this issue. > Guess I will not be installing this hotfix on a Windows 2003 Server.
|
