Microsoft KB Archive/287470

From BetaArchive Wiki
Knowledge Base


FIX: BizTalk Server HTTP Send Does Not Support Redirects

Article ID: 287470

Article Last Modified on 10/17/2003



APPLIES TO

  • Microsoft BizTalk Server 2000 Standard Edition



This article was previously published under Q287470

SYMPTOMS

When an HTTP send is performed from BizTalk Server to a redirected URL, the following error message is generated in the Application event log of the computer running BizTalk Server. In addition, the document being processed is placed in the Retry queue, and then placed in the Suspended queue after it fails all retries.

Source: BizTalk Server
Category: Document Processing
Event ID: 324

Description:
An error occurred in BizTalk Server.

Details:



An error occurred during transmission:
Request information:

Proxy:
Proxy port:80
URL:http://webserver/redirect.asp
Content-Type:text/plain; charset="utf-8"
User name:
Client certificate:
Request body:2551 Bytes
Timeout duration (seconds): 97
Error code:80004005
====== ERROR =====
The HTTP server returned an unexpected response: 302 Object Moved
The following response was received:

<head><title>Object Moved</title></head>
<body><h1>Object Moved</h1>This document may be found
<a HREF="/?scid=%2freceivestandard.asp">here</a>.</body>
                    

The server encountered a transport error while processing the messaging port "Port to ASP", which uses a transport component with a ProgID of "BizTalk.SendHTTPX.1".

All retry transmissions failed.

Unspecified error

The server could not finish processing messaging port "Port to ASP".

Suspended Queue ID: "{4BFC0A88-B529-4667-BB7F-5346BC2AF308}"

Unspecified error

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

299664 INFO: How to Obtain the Latest BizTalk Server 2000 Service Pack


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft BizTalk Server 2000 Service Pack 2.

Keywords: kbbug kbfix kbbiztalk2000sp2fix KB287470