We have this VBScript in our Classic ASP Page
function LoadAttachment(strFileName)
Dim objAttachmentStream, strFilePath
Dim ReadSuccess
aLocations = Split(AttachmentsRootUNC,";")
ReadSucess = false
for each location in aLocations
on error resume next
strFilePath = location & strFileName
set objAttachmentStream = Server.CreateObject("ADODB.Stream")
objAttachmentStream.Type = 1 'binary
objAttachmentStream.Open()
objAttachmentStream.LoadFromFile("\\mediaserver\media\1240939.jpg")
if Err.number = 0 then
ReadSuccess = true
Exit For
else
'Response.Write Err.number
'Response.Write Err.description
'Response.End
Err.Clear()
objAttacmentStream.Close()
set objAttachmentStream = nothing
end if
on error goto 0
next
if ReadSuccess then
set LoadAttachment = objAttachmentStream
else
set LoadAttachment = nothing
end if
End Function
Based on the 6 different scenarios below, we have concluded this must be a mis-configuration on our Windows 2008 IIS7 Web Server. However everything we have looked at has done nothing thus far. With so many changes to both Security, IIS, in Windows Server 2008 we have no idea where else to look or what other information may be relevant for this post.
Scenario 1: Access Failed
Server 1 (IIS 7.0 Web Server)
Windows Server 2008 Web Edition
Not Domain Member
Server 2 (Media Server)
Windows Server 2008 Web Edition
Domain Member
Scenario 2: Access Failed
Server 1 (IIS 7.0 Web Server)
Windows Server 2008 Web Edition
Not Domain Member
Server 3 (Media Server)
Windows Server 2003 Web Edition
Domain Member
Scenario 3: Access Successful
Server 1 (IIS 7.0 Web Server)
Windows Server 2008 Web Edition
Not Domain Member
Server 4 (Media Server)
Linux Variant (network storage system)
Not Domain Member
Scenarios 4-6 Access Successful
Server 5 (IIS 6.0 Web Server)
Windows Server 2003 Web Edition
Not Domain Member
Connects fine to servers 2, 3, and 4 (all different OS's)
I didn't want to provide too much meaningless information, but if there is anything I omitted, please let me know.