Bea-3xxxxx error code

Transmission runtime error
（BEA-380000 to BEA-38099）
BEA-380000
General transmission error
XML Details : Received an error response
（ When it appears in the publish operation ）
Message flow runtime error code (382000...382499)
BEA-382000
General runtime error

BEA-382030
General parsing of the binding layer failed （ for example , Sent to the XML The service message is not XML）

BEA-382031
Do not conform to the WS-I standard

BEA-382032
The message must be soap:Envelope
XML Details : Received a non SOAP Or invalid envelope

BEA-382033
soap:Envelope Must contain soap:Body

BEA-382040
Is the context variable "{0}" Failed to allocate value . The value must be {1} An example of

BEA-382041
Is the context variable "{0}" Failed to allocate value . The variable is read-only .

BEA-382042
Is the context variable "{0}" Failed to allocate value .{1}

BEA-382043
Update context variables "{0}" The value of failed ：{1}

BEA-382045
Initialize context variables "{0}" The value of failed ：{1}

BEA-382046
Set the context variable "{0}" Values of are grouped to XML Failure ：{1}

BEA-382100
General binding error while processing inbound request

BEA-382101
General binding error while preparing inbound response

BEA-382102
General binding error when preparing outbound request

BEA-382103
General binding error when processing outbound response

BEA-382104
Cannot serve {0} Prepare to request metadata

BEA-382105
Cannot serve {0} Prepare response metadata

BEA-382150
Unable to schedule service {0} Request

BEA-382151
Unable to schedule to unknown service ：{0}
Operation error code (382500...382999)
BEA-382500
ALSB Service annotation operation received SOAP Fault response .
XML Details : Receive a SOAP Fault response

BEA-382501
ALSB The service callout operation has received an unrecognized response .XML Details : Received an unrecognized response

BEA-382502
ALSB The service tag has received an error response from the server XML Details : Received an unknown error response

BEA-382505
ALSB Validation operation validation failed .
XML Details : Validation failed

BEA-382510
Update variables "{0}" when ALSB Allocation operation failed ：{1}

BEA-382511
Update variables "{0}" when ALSB Delete operation failed ：{1}

BEA-382512
Update variables "{0}" when ALSB Insert operation failed ：{1}

BEA-382513
Update variables "{0}" when ALSB Replace operation failed ：{1}

BEA-382514
Update variables "{0}" when ALSB Rename operation failed ：{1}

BEA-382515
in the light of Java Method "{0}" The annotation of results in an exception ：{1}

BEA-382516
Calculation for Java Method "{0}" The expression of the annotation of failed . Parameter index ：{1}, abnormal ：{2}

BEA-382517
take Java Failed to assign the result of annotation to variable . Method ：{0}, Variable ：{1}, abnormal ：{2}

BEA-382518
call Java Method "{0}" Security exception occurs during . Service account ：{1}.{2}

BEA-382600
ALSB The publish operation received an error response ：{0}
Security error code (386000...386999)
BEA-386000
General security error . The possible reasons are as follows ：
Custom tag or user name configured / Password authentication , But the authentication has passed WS Safe execution .

BEA-386100
Authentication has failed . The possible reasons are as follows ：
The XPath Configured for body or title , But there is no such message part （ The binding layer returns empty content ）.
XPath The engine is evaluating XPath Expression threw an exception .
user name XPath Or code XPath The result is non TEXT or ATTR Node of type .
XPath Return multiple nodes .
User name retrieved / password , But authentication has failed .
Custom tag retrieved , But the identity declaration has failed （CSS The identity declaration service raises LoginException Or any other exception ）.

BEA-386101
Missing authentication token . The possible reasons are as follows ：
user name XPath Or code XPath Return empty result or empty string .
Custom tags XPath Return null result 、 Empty attribute value or empty text value .

BEA-386102
Message level authorization denied . The possible reasons are as follows ：
The message level access control policy denies access to the proxy service .

BEA-386103
The proxy service operation selection algorithm cannot determine the operation name in the request or returns an invalid operation （ Not in WSDL Medium or empty ）. The possible reasons are as follows ：
Error in calculation operation .
The operation selection algorithm returns empty content .
The operation returned by the operation selection algorithm is not WSDL Declared operation .

BEA-386200
routine Web Service Security error

BEA-386201
appear Web Service Safety failure [<error-code from WSS fault>][<fault-string from WSS-fault>] XML Details : appear WS-Security fault

BEA-386400
Regular outbound Web Service Security error

BEA-386401
Unable to convert outbound message to SOAP

BEA-386402
Unable to determine outbound operation

BEA-386420
An error occurred while generating the security header Web Service Security error

BEA-386440
An error occurred while processing the security header Web Service Security error

BEA-386460
Web Service Security policy validation error
UDDI Error code (394500...394999)
BEA-394500
An error was encountered while importing resources

BEA-394501
Query business entity UDDI An error was encountered while registering

BEA-394502
initialization UDDI Error encountered while servicing

BEA-394503
Error initializing query port

BEA-394504
An error was encountered while publishing this service

BEA-394505
Can't connect to UDDI The registry

BEA-394506
Query business service UDDI An error was encountered while registering

BEA-394507
The registry name contains characters that are not allowed

BEA-394508
Release URL The lack of UDDI Registry configuration

BEA-394509
The configured service account is invalid

BEA-394510
Cannot import resources while importing Services

BEA-394511
Validation exception occurred while creating the service definition during service import

BEA-394512
General error encountered while importing resources

BEA-394513
Internal error encountered while importing resources

BEA-394514
Cannot create while importing service FTP Endpoint Configuration

BEA-394515
Failed to create email endpoint configuration when importing service

BEA-394516
When importing services, at the access point URL Possible syntax errors in

BEA-394517
Resolve during import service InstanceParms When you encounter an error

BEA-394518
Failed to create file endpoint configuration when importing service
————————————————
Copyright notice ： This paper is about CSDN Blogger 「 Game paradise IT」 The original article of , follow CC 4.0 BY-SA Copyright agreement , For reprint, please attach the original source link and this statement .
Link to the original text ：https://blog.csdn.net/qq_32660307/article/details/84984105