Catalyst Knowledge Base Articles

Unable to Resolve an IPv6 Address on Windows XP

Mon, 22 Aug 2011 18:01:13 GMT

When attempting to resolve an IPv6 address on a Windows XP or Windows Server 2003 system, either explicitly or by specifying an IPv6 address as the host address when establishing a connection, the method or function fails with an error indicating that the address is invalid. The same address can be resolved successfully on a Windows 7 or Windows Server 2008 system.

Unable to Restart Text File Transfers

Tue, 16 Aug 2011 21:07:20 GMT

Attempting to restart a text file transfer by specifying a byte offset fails, with the error code indicating that the operation is not supported. The server rejects the request because it will not accept the REST command if the current file transfer mode is set to ASCII and this error is reported by the SocketTools component back to the application.

Unexpected Error Requesting File Size After File Transfer

Tue, 16 Aug 2011 21:06:23 GMT

The client application is unable to determine the size of a remote file on an FTP server. This occurs during or after a text file has been transferred. Previous transfers of binary files from the same server report the correct file size. Attempting to explicitly get the size of a file prior to a transfer can result in an error indicating that the file does not exist, even though it does and can be downloaded successfully.

Poor Performance Submitting Messages to Exchange Server

Tue, 16 Aug 2011 21:04:28 GMT

Submitting an e-mail message to a Microsoft Exchange Server 2007 (or later version) is significantly slower than expected, where each message submission can take up to 10 seconds to complete. This problem does not occur when submitting messages to other types of mail servers, including earlier versions of Exchange Server.

Understanding the INTERNET_ADDRESS Data Structure

Wed, 27 Jul 2011 20:23:27 GMT

With the release of SocketTools 7.0 and support for both IPv4 and IPv6 networks, a new data structure has been introduced named INTERNET_ADDRESS. This article will discuss how the structure is used and the coding changes required when upgrading an application to use the current version of SocketTools.

Unable to Reference SocketTools C++ Classes

Wed, 27 Jul 2011 20:23:21 GMT

Compiling an application that uses the Microsoft Foundation Classes (MFC) and SocketTools fails with error C2065, indicating that the class being referenced is undeclared. The compiler may also display other warnings or errors, such as the Windows.h header file being already included. To resolve this issue, include the SocketTools header file after you have included the StdAfx.h or AfxWin.h header file.

Compilation Errors When Using Visual C++ 6.0

Wed, 27 Jul 2011 20:23:13 GMT

Compiling an application using Microsoft Visual C++ 6.0 and SocketTools 7.0 can result in error C2501 "missing storage-class or type specifiers" during compilation. This error occurs because earlier versions of Visual C++ and the Windows SDK did not define the DWORD_PTR data type, which is used throughout the SocketTools header file. This error can also occur with other versions of Visual C++ if the application was originally written in Visual C++ 6.0 and the project was imported into a later version of the compiler.

Unable to Establish Connection From Windows XP

Wed, 27 Jul 2011 20:23:06 GMT

Attempting to establish a connection with SocketTools 7.0 using a valid host name on a system running Windows XP fails, either with the connection timing out or being refused. The same program can connect successfully when run on a later version of Windows, such as Windows 7 or Windows Server 2008. This problem has been corrected in SocketTools 7.1 and it is recommended that all developers who continue to support the Windows XP platform upgrade to this release.

Handling Aborted Network Connections

Mon, 24 May 2010 18:55:42 GMT

When an application sends or receives data, the operation may fail with an error indicating that the connection has been aborted or the connection has been reset. Subsequent attempts to send or receive data will fail, and no further network events are generated for asynchronous connections.

These errors are fatal conditions which indicate that the connection to the remote host has been lost. The only option available to the application is to close its end of the connection, using the corresponding Disconnect function in the API or the Disconnect method in the component.

Type or Namespace Name SocketTools Not Found

Tue, 27 Apr 2010 23:21:19 GMT

When attempting to build an application that references one or more SocketTools assemblies, the compiler returns the error:

The type or namespace name 'SocketTools' could not be found (are you missing a using directive or an assembly reference?)

An error may also be displayed when viewing the project references, indicating that one or more assemblies cannot be found. This error most commonly occurs when a project has been moved from one development system to another, or after a service pack update for the SocketTools .NET components was installed.

Unexpected Error When Reading a Datagram

Tue, 27 Apr 2010 22:46:39 GMT

When the SocketWrench library or component is used to read a datagram, the function or method fails with an error indicating that the connection has been reset. For the SocketWrench API, this would be indicated by the InetReadEx function failing, with the last error code set to 0x80042746. With the SocketWrench ActiveX control and .NET component, this would be indicated by the Read or ReadFrom method failing, with the last error code set to 10054.

This error may occur when you send a datagram to a non-existent or unreachable IP address and a router sends an ICMP "destination unreachable" error datagram in response. When this occurs, the socket will be flagged as readable, however attempts to read a datagram will result in this error. This behavior is by design, and indicates that the remote host address is not valid. When this error occurs, you should close the socket by calling the InetDisconnect function or Disconnect method, and then recreate the datagram socket.

Compilation Error After Updating SocketTools .NET Components

Tue, 27 Apr 2010 22:23:31 GMT

After updating the components SocketTools .NET, either by installing a service pack update or applying a hotfix, a project fails to compile with the error "Could not resolve this reference. Could not locate the assembly ... Check to make sure the assembly exists on disk."

This error occurs because the SocketTools .NET assemblies have a strong name, which means they are strictly versioned and digitally signed. Because your project was built using an earlier version of the component, the reference to the component cannot be resolved.

To correct this problem, remove the reference to the previous version of the component by selecting Project | Properties from the menu, then select the References tab to show a list of referenced assemblies. Select the SocketTools assembly and click on the Remove button. Then click on the Add button to add the current version of the assembly back to the project and then select Build | Rebuild Solution from the menu.

Deploying SocketTools .NET Applications Using ClickOnce

Tue, 27 Apr 2010 18:45:30 GMT

If you wish to publish a .NET application that uses once or more SocketTools .NET components, you should include both the class assemblies that are referenced, and the SocketTools.Interop.dll library as part of your project. The SocketTools assemblies and shared library should be deployed in the same folder as your application executable.

InvalidOperationException Error Executing .NET Application

Tue, 22 Dec 2009 19:19:22 GMT

When attempting to run an application that uses one of the SocketTools .NET components, an InvalidOperation exception is generated. Typically the error message reads:

An error occurred creating the form. See Exception.InnerException for details. The error is: An attempt was made to load a program with an incorrect format. (Exception from HRESULT: 0x8007000B)

If the exception is not handled, a message box will be displayed that contains additional information about the error and then the program terminates.

Password Required for Secure Shell (SSH) Connection

Wed, 16 Dec 2009 17:56:36 GMT

When attempting to establish a connection without specifying a password, an error is returned indicating that a password is required. The SocketTools Secure Shell (SSH) library, ActiveX control and .NET component requires that you provide a password to authenticate the client session.

Unable to Connect to SuSE Linux Using Secure Shell Protocol

Tue, 15 Dec 2009 00:31:37 GMT

When attempting to establish a connection using the Secure Shell (SSH) protocol to a SuSE Linux system, the connection fails with an error indicating that the connection could not complete. This error affects both the SSH component and file transfers using the SFTP (FTP+SSH) protocol.

Modifying a Form in Visual FoxPro 5.0 Generates Error 0x800A018A

Tue, 15 Dec 2009 00:23:06 GMT

When modifying a form in Visual Foxpro 5.0 that contains one of the SocketTools ActiveX controls, the following error is displayed:

OLE error code 0x800a018a: Unknown OLE status code

This error typically only occurs when changes are being made to an existing form in older versions of Visual Foxpro.

This a COM error that corresponds to CTL_E_GETNOTSUPPORTED, which indicates FoxPro is trying to ask for the value of a property that is not available at the time the control is being instantiated. This error can be shown in older versions of Foxpro when it tries to access a write-only property at design time. It does not interfere with the operation of the control at runtime.

SocketTools FTP Functions Fail When Application Uses WinInet

Wed, 02 Dec 2009 22:38:06 GMT

An application written in C/C++ which uses the SocketTools FTP API does not function correctly when it also uses the WinInet API. Certain functionality may not be available, or the application may fail with a general protection exception. For example, the FtpGetFile and FtpPutFile functions may not return an error, but the file is not transferred.

Domain Name Service Component Returns Incorrect Address

Wed, 02 Dec 2009 22:21:42 GMT

When using the Domain Name Service library, ActiveX control or .NET component, a valid host name is not resolved to the correct IP address. This problem manifests on systems that are configured with a primary DNS suffix, or have joined a domain and the DNS suffix has changed. It may also occur when a local domain name has been explicitly specified by the application.

Unable to Register ActiveX Controls on 64-bit Windows

Mon, 02 Nov 2009 18:50:27 GMT

When attempting to manually register an ActiveX control on 64-bit Windows, an error is displayed indicating it is not an executable file and no registration helper is registered for this file type.

On 64-bit versions of Windows, the \windows\system32 folder contains 64-bit executables and you cannot register 32-bit ActiveX controls using the 64-bit version of regsvr32.exe. A 32-bit ActiveX control should be copied to the \windows\syswow64 folder, and the regsvr32.exe utility in that folder should be used to register the control.

Licensing Error When Initializing SocketTools .NET Class

Fri, 23 Oct 2009 17:24:33 GMT

The Initialize method fails when a valid runtime license key is specified. The SocketTools .NET class initializes successfully if no runtime license key is provided on the development system, however the application cannot be redistributed.

This error typically indicates that an incorrect version of the SocketTools.Interop.dll library is being loaded by the application. When SocketTools .NET is installed, an entry is added to the PATH environment variable which specifies the path to the SocketTools assemblies. If a previous version of SocketTools .NET was installed on the development system, the application may load the wrong version.

Unable to Establish SMTP Connection with Mail Server

Fri, 23 Oct 2009 17:08:32 GMT

An application which uses the Simple Mail Transfer Protocol to submit e-mail messages for delivery fails with error 0x8004274C (10060) or error 0x8004274D (10061). This indicates that the connection has timed out, or was refused by the remote host.

Error 0x80043032 When Accepting Client Connections

Fri, 23 Oct 2009 16:14:41 GMT

When using the SocketWrench Internet Server API, the error ST_ERROR_THREAD_CREATION_FAILED is returned whenever a client session is started.

This error indicates that the CreateThread function has failed, typically becuase there is not enough memory to allocate a stack for the new thread. Each active client session is managed in a seperate thread which has its own stack. If the default stack size is set to a high value and there are a large number of client connections, it can result in this error. The solution is to reduce the stack size or limit the maximum number of clients which can establish a connection with the server.

Note that if you are using the PowerBasic language, each thread that is created will use the same stack size that is set for the main thread. Using the #STACK statement to set the stack size to a large value can result in this error

Using SocketTools ActiveX Controls With Registration-Free COM

Thu, 22 Oct 2009 22:31:24 GMT

Normally, an ActiveX control stores information about itself in the registry, and that information is used when an application needs to create an instance of the control. This process is called COM registration, and ActiveX controls are self-registering, which means they have the ability to register themselves with the system. However, COM registration requires elevated privileges, and typically involves an installer which loads the ActiveX control to perform the registration process.

Registration-free COM stores information about the control in an application manifest, rather than the system registry. This can simplify deployment and it also ensures that the application loads the version of the control that it was built with. The developer can avoid situations in which a different version of the control is installed on the system at a later point, resulting in conflicts with their application.

External Application Manifest Not Regonized

Thu, 22 Oct 2009 22:21:28 GMT

When using an external application manifest to set the requested privilege elevation level, the system doesn't recognize it unless you move the executable to a different folder.

When you install a legacy Windows application that does not have an embedded manifest, you may create an external manifest named application.exe.manifest that specifies whether the program requires elevated privileges. However, after creating the manifest, the system doesn't recognize the manifest until you install the application in a different folder.

To improve performance, the operating system will cache the manifest as part of the application's activation data. Because there wasn't a manifest available the first time the program was loaded from the current location, it will not check for an external manifest whenever the program is executed again. When you move the location of the program or change its timestamp, the entry for the executable won't be found in the cache and the system will check for the manifest again.

Installation Fails Because IKernel.exe is Read-only or Corrupted

Thu, 22 Oct 2009 22:18:01 GMT

When installing a product, the installation fails with an error indicating the InstallShield engine (IKernel.exe) is read-only or corrupted.

The setup program copies the InstallShield engine files to the hard disk during installation. By default, these files are copied to the folder C:\Program Files\Common Files\InstallShield. This folder is used as a temporary folder during the installation process. After you install the program, the contents of this folder are no longer needed or used.

This error may occur if the InstallShield engine or one of its component files in the C:\Program Files\Common Files\InstallShield\Engine folder is damaged, corrupt, or has read-only permission. This error may also occur if one of the InstallShield components was left on the system by an older version of the InstallShield installer that are incompatible with the current version of InstallShield used by the SocketTools installer. It is recommended that you either rename or delete this folder and rerun the setup. The InstallShield installer will then replace or install the correct engine files if they are not found on the computer.

Application Using SocketTools .NET Assemblies Loads Slowly

Thu, 22 Oct 2009 22:16:21 GMT

When using the SocketTools .NET components in your application, the program takes several seconds to load. When all references to the SocketTools asseblies are removed, the application loads immediately.

The SocketTools .NET assemblies are digitially signed using Authenticode, which identifies the components and ensures that they have not been tampered with. This problem occurs because the .NET CLR validates signed assemblies by performing a CRL (Certificate Revocation List) check. When the assembly is loaded, the CRL is downloaded and the Authenticode certificate is checked to determine if it has been revoked and is no longer valid. This can cause a delay as the CRL check is made, and can result in increased load times.

System.SecurityException Error Using ASP.NET

Thu, 22 Oct 2009 22:12:27 GMT

The System.SecurityException error occurs when a SocketTools .NET component is used with an ASP.NET application, displaying the following message:

The application attempted to perform an operation not allowed by the security policy. To grant this application the required permission please contact your system administrator or change the application's trust level in the configuration file.

This error indicates that the server is not configured for Full Trust. The SocketTools .NET components require unrestricted access to specific system resources such as the networking subsystem and system registry.

Network Performance on Windows Vista

Wed, 15 Jul 2009 19:49:23 GMT

An application running on the Windows Vista platform will occasionally experience long delays when receiving data. The network operation can fail with a timeout error, or incomplete data is returned. The same application running on Windows XP and Windows 2000 functions correctly.

Windows Vista introduced a new feature called "receive window auto-tuning" which was designed to dynamically adjust the TCP/IP stack's receive window size based on changing network conditions. However, some users have reported that this feature can result in long delays, timeouts and connection problems with some applications and network routers.

Networking Subsystem Not Initialized

Mon, 13 Jul 2009 19:01:04 GMT

Attempting to initialize the .NET class, ActiveX control or library fails with an error indicating that the networking subsystem cannot be initialized. The application cannot establish a connection, and subsequent attempts to reinitialize the component also fails with the same error message.

This error can indicate that either the component has not been initialized, or the component is unable to initialize the TCP/IP stack, which is required to establish network connections on the local host.

File Transfer Fails With Authentication Error

Wed, 08 Apr 2009 23:14:40 GMT

When attempting to transfer a file to an HTTP server using the File Transfer .NET component, an error is returned indicating that the user does not have permission to access the file. The UserName and Password properties are set to the correct values, however the server will not authenticate the client session. The file transfer is successful if the HTTP server does not require authentication.

This is known issue with version 6.0 build 6010 and earlier builds of the Catalyst File Transfer .NET product. It is recommended that all developers using this component install this hotfix.

File Upload Fails With Access Denied Error

Wed, 30 Jan 2008 00:21:39 GMT

When attempting to upload a file to an FTP server using the PutFile method in the Catalyst File Transfer .NET component, an error is returned indicating that access is denied. However, the user does have the appropriate access rights and the file can be uploaded to the same location on the file server using another FTP client application.

The PutFile method can fail under some circumstances, returning a value of false with the last error code set to errorAccessDenied (10013). This is a result of an internal error in handling the transfer process, and does not indicate a problem with the actual access rights for the authenticated user.

This problem only occurs with the File Transfer .NET component, not the FTP client component in the SocketTools .NET product. It also only occurs when uploading a file using the File Transfer Protocol (FTP), not when using the Hypertext Transfer Protocol (HTTP).

IKernel.exe Product Installation Error

Thu, 26 Jul 2007 20:32:07 GMT

When installing a product on Windows 2000 or a later version of the Windows operating system, the following error is displayed:

Error installing iKernel.exe. Specified network name is no longer available.

This error typically occurs when the InstallShield engine named IKernel.exe or one of its components are flagged as read-only or may have been corrupted. The setup program copies InstallShield engine files to the hard disk during the installation process. If these files cannot be copied or loaded by InstallShield, this error message will be displayed.

Cannot Authenticate Secure IMAP4 Session

Thu, 26 Jul 2007 20:31:37 GMT

When attempting to connect to a secure IMAP4 server, an error is returned indicating that the user credentials cannot be authenticated. A connection can be successfully established with Microsoft Outlook or another mail client using the same credentials.

Base64 Encoding Corrupts Multipart Header Section

Thu, 26 Jul 2007 20:30:52 GMT

If a multipart email message contains more than one base64 encoded section, the header sections for subsequent message parts may be corrupted. This can result in incorrect header values, and may result in the application terminating abnormally.

Product Installation Terminates Unexpectedly

Mon, 16 Apr 2007 21:01:11 GMT

When attempting to install a product, the installation fails abnormally at the beginning of the setup process. A message may be displayed which indicates a general protection fault, or the installer may fail silently with no error messages displayed.

Evaluation Licensing Error in Service Applications

Mon, 16 Apr 2007 20:45:55 GMT

During the evaluation period, an instance of the component or library can be initialized successfully when used in an application but fails when used as a standard Windows service. The error code value that is returned indicates that the product is not licensed.

Daylight Savings Time Changes

Tue, 06 Mar 2007 22:18:45 GMT

The U.S. Energy Policy Act of 2005 extended Daylight Saving Time (DST) in the United States by approximately four weeks. DST will now start three weeks earlier on March 11, 2007 and will end one week later on November 4, 2007. These changes may cause applications to report an incorrect timezone value under some circumstances.

Memory Leak When Calling HttpGetSecurityInformation

Tue, 16 Jan 2007 00:11:02 GMT

If an application repeatedly calls the HttpGetSecurityInformation function to obtain information about a server's certificate, a memory leak can occur.

The HttpGetSecurityInformation function is used to obtain information about the status of a secure connection, as well as specific information about the certificate that was issued to the server that the application has connected to. Normally this function is called after a connection has been established to determine if the certificate is valid and has not expired.

If an application repeatedly calls this function, or establishes a number of different secure connections to various servers over its lifetime, a memory leak can occur because a certificate context is not being released properly under some circumstances. Applications that use this function should install the update available for this library. This does not affect applications which use the standard Library Edition or do not establish secure connections.

Cannot Modify Examples in Visual Studio 2005

Mon, 15 Jan 2007 22:12:19 GMT

When attempting to modify an example program or view a form under Windows Vista, an error message similar to the following is displayed:

There is no editor available for C:\Program Files\...
Make sure the application for the file type (.vb) is installed

This error message is only displayed if the product was installed using the default installation path under C:\Program Files and not if it was installed into an alternate location.

Cannot Create or Delete Licenses Using License Manager

Mon, 15 Jan 2007 19:36:58 GMT

Creating or deleting a license using the License Manager utility under Windows Vista can fail with an error that indicates a problem with the registry, or can cause the utility to become non-responsive.

Secure Writes Cannot Exceed 16384 Bytes

Sat, 13 Jan 2007 00:19:33 GMT

SocketTools uses Microsoft's CryptoAPI and the SChannel provider to implement secure SSL/TLS connections. The data that is written by the application to the remote host is encrypted using a function called EncryptMessage. A limitation of the EncryptMessage function is that it cannot encrypt more than 16,384 (16K) of data in a single operation.

Registry Handle Leak in SocketWrench and SocketWrench .NET

Fri, 12 Jan 2007 22:43:54 GMT

Under certain circumstances, a handle to a registry key may be left open when an instance of the SocketWrench ActiveX control or SocketWrench .NET class is created. This handle leak typically has the greatest impact on applications that are designed to run for long periods of time and dynamically create multiple instances of the component.

Duplicate Accept Events Generated on Windows 2000 and Windows XP

Tue, 11 Jul 2006 21:35:13 GMT

Under certain circumstances, a server application using non-blocking (asynchronous) sockets on Windows 2000 or Windows XP may receive duplicate accept event notifications. If the SocketWrench ActiveX control is used, this results in multiple OnAccept events being generated for the same client connection. If the dynamic link library (DLL) is being used, multiple INET_EVENT_ACCEPT notifications may be sent to the server application.

Directory Listing Does Not Include Hidden Files

Sat, 03 Jun 2006 23:38:51 GMT

When directory listing is requested from an FTP server, not all files and subdirectories are listed. Normally, only visible files and subdirectories will be returned by the server when a file list is requested.

Application Hangs During Large Data Transfers

Tue, 30 May 2006 22:13:52 GMT

When transferring a large amount of information over the network, the application will appear to hang and stop exchanging data, or the transfer will abort unexpectedly.

Some network adapters have a configuration option called Checksum Offload which is used to reduce the load on the system's processor by offloading large TCP packets for segmentation. In some cases, this can cause an application that is exchanging a large amount of information, such as uploading or downloading a large file, to hang and stop transferring data or abort the connection to the server.

Operation In Progress Error When Retrieving Messages

Fri, 05 May 2006 02:43:53 GMT

When retrieving message headers or complete messages from an IMAP server, error 10036 (0x80042734) may occur and the message data is not returned to the client. The error condition indicates that a blocking operation is already in progress and only occurs when the message is new and has not been previously accessed on the server. Subsequent attempts to access the message succeed without an error.

Memory Leak When File Download is Unable to Create Local File

Fri, 05 May 2006 02:42:45 GMT

When downloading a file from a server, if the local file cannot be created due to an invalid network path or insufficient privilege to create the file, a memory leak can occur.

OLEException Raised When Using ActiveX Controls in REALbasic

Mon, 17 Apr 2006 23:00:11 GMT

When calling certain methods in the SocketTools ActiveX controls using the REALbasic programming language, an error message is displayed indicating that an unhandled OLE exception has been raised and the error code -2147352567 is specified in the error message.

Error Handling Using ReadLine and WriteLine

Mon, 17 Apr 2006 22:59:58 GMT

The ReadLine and WriteLine methods in the SocketWrench component provide a simple way to read textual data up to a terminating carriage-return/linefeed byte sequence. However, unlike the Read and Write methods, they do not return a numeric value which specifies the number of bytes read or written. Instead these methods return a boolean value of true or false. If the application needs to be able to handle specific error conditions, special consideration should be taken when using these methods.

Memory Exception Occurs Using InetReadStream

Mon, 17 Apr 2006 22:59:22 GMT

When calling the InetReadStream function using the INET_STREAM_DEFAULT option an unhandled memory exception occurs and the application terminates.

File Transfer Protocol Component Returns Error 12255

Mon, 17 Apr 2006 22:58:52 GMT

When using the File Transfer Protocol (FTP) component, an attempt to read a directory listing or transfer a file fails with the LastError property returning a value of 12255.

Cannot Initialize Properties in FoxPro Form Load Event

Mon, 17 Apr 2006 22:54:16 GMT

When attempting to set the value of a control property in the FoxPro form Load event handler, an error is returned indicating that the property is an unknown member of the control.

Delivery Status Notification Messages Not Returned

Sat, 15 Apr 2006 22:11:49 GMT

When using the Simple Mail Transfer Protocol (SMTP) component or library, no delivery status messages are returned to the sender when one or more Delivery Status Notification (DSN) options are specified.

Application Freezes When Updating User Interface in .NET

Thu, 13 Apr 2006 20:32:15 GMT

When updating a user interface component from an event handler in another thread, the application can become non-responsive.

Bad Variable Type Exception When Calling Method

Wed, 22 Feb 2006 16:43:01 GMT

When calling a method in an ActiveX/COM component Windows 2000 or earlier versions, an unexpected COM exception is thrown indicating that a "bad variable type" was passed to the method. The same program works correctly under Windows XP and later versions. This error is most likely encountered when using the component in Visual Studio.NET, but may also occur in other development environments.

File Transfer Fails When Command Channel Cleared

Wed, 30 Nov 2005 20:14:01 GMT

When attempting to securely transfer a file to a server after the command channel has been cleared, the transfer may immediately fail with an error indicating that a secure session could not be established. Standard file transfers are unaffected, as are secure transfers where the command channel remains encrypted.

File Access Rights Reset After Patch Applied

Thu, 29 Sep 2005 18:25:28 GMT

After applying a patch on a Windows XP or Windows Server 2003 system, the permissions for the patched file are reset to the defaults for the current process. This can prevent an application from reading or updating the file if it cannot access or modify it using the default access rights.

Uploading Files To Microsoft Internet Information Server (IIS)

Fri, 12 Aug 2005 21:06:06 GMT

When attempting to upload a file to an IIS webserver using the HTTP PUT command, the transfer fails with a 404 error. The server administrator had used to the IIS Lockdown Tool to secure the server.