Site Server Express - Posting Acceptor Administration

Article
08/28/2007

Optimal Functioning of Posting Acceptor

This section contains information necessary to maintain optimal functioning of Posting Acceptor. This includes performance monitoring tables and other important information you must provide for users to help them post Web content properly.

Performance Monitoring

Posting Acceptor exposes the following Performance Monitor counters, Windows NT events, and registry keys to track the activity of multiple components and operations.

Performance Monitor Counters

For performance monitoring on Windows NT, the Posting Acceptor exports one object called "RFC 1867 Posting Acceptor." This object contains the following counters.

Name	Explanation
Current Posts	The number of current posts being processed by the acceptor.
Unresolved Posts	The number of current posts awaiting commitment from the clients.
Maximum Posts	The maximum number of instantaneous posts over the lifetime of the acceptor.
Total Posts Received	The number of posts received up to this point.
Total Successful Posts	The number of successful posts received up to this point.
Total Re-posts Done	The number of reposts performed up to this point.
Total Files Received	The number of files received up to this point.
Total Failed Posts	The number of posts that failed so far.
Total Bytes Received	The number of bytes received so far.
Successful Posts/Sec	The rate of successful posts.
Re-posts/Sec	The rate at which reposts are done.
Posts Received/Sec	The rate at which posts are received.
Files Received/Sec	The rate at which files are posted.
Failed Posts/Sec	The rate at which posts are failing.
Bytes Received/Sec	The rate at which bytes are received.

Windows NT Events

Posting Acceptor logs a limited number of Windows NT events to notify you of failed posting or reposting attempts. The logs detail the following information:

Who attempted to post.
What URL was specified.
What error or warning was encountered.

Event ID	0x2201
Meaning	Cannot move file to its final destination. Further processing is stopped.
Cause	NA
Solution	None

Event ID	0x2202
Meaning	TargetURL is invalid.
Cause	NA
Solution	None

Event ID	0x2203
Meaning	No valid files received.
Cause	NA
Solution	None

Event ID	0x2204
Meaning	Cannot initialize OLE libraries.
Cause	NA
Solution	None

Event ID	0x2205
Meaning	The query string is invalid.
Cause	NA
Solution	None

Event ID	0x2206
Meaning	This is your server and not the specified server in the TargetURL.
Cause	NA
Solution	None

Event ID	0x2207
Meaning	File posted successfully.
Cause	NA
Solution	None

Event ID	0x2208
Meaning	Reposting to URL failed.
Cause	NA
Solution	None

Event ID	0x2209
Meaning	Reposting to URL successful.
Cause	NA
Solution	None

Event ID	0x220A
Meaning	Reposting to URL successful. No content came back from the server.
Cause	NA
Solution	None

Event ID	0x220B
Meaning	Your transaction is either invalid or has expired. Please try reposting your files again.
Cause	NA
Solution	None

Event ID	0x220C
Meaning	Your files cannot be posted at this time.
Cause	There are too many open transactions.
Solution	Please try reposting your files again later.

Event ID	0x2281
Meaning	Cannot move file to its final destination. Further processing is stopped.
Cause	The user may not have adequate permissions on the machine to move posted files to a final destination.
Solution	Check the connected user's permissions to see if they are allowed to create directories and files in the specified destination.

Event ID	0x2282
Meaning	TargetURL is invalid.
Cause	The TargetURL cannot be resolved.
Solution	Ask the user to specify the correct TargetURL. Also, confirm that you have correctly setup the URL in the postinfo.asp and upload.asp files.

Event ID	0x2283
Meaning	No valid files received.
Cause	The post contained no files. The user is sending posts that do not contain any valid (non-empty) files.
Solution	None

Event ID	0x2284
Meaning	Cannot initialize OLE libraries.
Cause	Initialization of OLE failed. This may be a bad operating system installation, or the connected user is not able to use OLE on this system.
Solution	None

Event ID	0x2285
Meaning	The query string is invalid.
Cause	The query string (part of the PostingURL) is invalid.
Solution	Tell the user to specify the correct PostingURL. Also, confirm that you have correctly setup the URL in postinfo.asp and upload?.asp files.

ID	0x2286
Meaning	This is your server and not the specified server in the targeted URL.
Cause	Someone is attempting to post files to a target server that is not yours.
Solution	Tell user to specify the correct TargetURL. Also, confirm that you have correctly setup the URL in postinfo.asp and upload?.asp files.

ID	0x2288
Meaning	Reposting to specified repost URL failed.
Cause	An attempted repost of the data to the Re-postURL failed.
Solution	Check the Re-postURL for accuracy.

ID	0x228A
Meaning	Reposting to specified Re-postURL successful. No content came back from the server.
Cause	The repost was successful. No HTML content came back from the server.
Solution	May be intentional. If not intentional, check the Re-postURL for accuracy.

ID	0x228B
Meaning	User specified transaction is either invalid or has expired.
Cause	An invalid session (transaction) ID was sent by the client. The client stayed disconnected for more than the allowed transaction timeout specified in the registry.
Solution	None

ID	0x228C
Meaning	There are too many open transactions to complete the user's request.
Cause	Too many users are trying to post simultaneously.
Solution	If your server has adequate space, increase the appropriate value limit in the registry.

ID	0x22FC
Meaning	Transaction ID has expired.
Cause	The user never committed the transaction so it expired.
Solution	None

ID	0x22FD
Meaning	Unknown error was encountered.
Cause	An internal error occurred.
Solution	None

ID	0x22FE
Meaning	Unknown error was encountered.
Cause	NA
Solution	None

Registry Keys

Microsoft Posting Acceptor contains a single registry key: HKLM\Software\Microsoft\WebPost\Acceptors\CPSHost

The registry contains the two values that you can adjust to suit your needs. For more information, see the section "Configuring Outstanding Posts," in this document:

OpenTransactionsTimeout. This controls maximum outstanding post duration. (Default is 600 seconds or five minutes.)
MaximumOpenTransactions: This controls maximum outstanding posts. (Default is 200.)

What to Tell Content Providers Posting To Your Server

Depending upon the type of browser used by your content providers, you must furnish them with certain information to make sure that their files are successfully posted.

Posting Information for WebPost Clients

If a content provider is publishing to your server with the WebPost API, you must convey the name of the server to which content will be posted. If you do not specify your PostInfo file, you must also tell them the PostingURL and TargetURL. WebPost API performs a GET against the virtual root of the TargetURL server to determine the location of the PostInfo file on the server. The WebPost API then retrieves the PostInfo file and parses out the PostingURL and TargetURL if they were specified earlier. If either the PostingURL or the TargetURL were not specified, the content provider must enter that information manually in Web Publishing Wizard.

Posting Information for Netscape Navigator and Other HTTP Clients

If a user is publishing to your hosting server with Netscape Navigator or another HTTP posting method, content is posted through the form that is embedded in the uploadN.asp sample page and is provided to the user. The PostingURL is specified by the action field in that form and the TargetURL is specified by the "TargetURL" form variable.

Note This procedure is optional. You may accept the default, https://yourserver/users/username, or select another URL.