I can't place a message in a non-transactional MSMQ on a server in our DMZ using HTTP. In the IIS logs I'm getting: 2013-05-15 20:29:54 W3SVC1 192.168.32.XXX POST /msmq/private$/newprivate - 80 - 170.115.XXX.XXX - 403 4 5
Based on the 403 I'm thinking that I don't have permission to the queue (or the MQISE.DLL)
I've added permissions to the following accounts: IWAM, IUSR, NETWORK, NETWORK SERVICE and I still can't access it. It works if I add a message on the box.
Any suggestions? Thanks in advance.
Are you sending from a transactional queue to a non-transactional queue? This will drop the message. Turn on negative source journalling for the message. Set the UseDeadLetterQueue of the message to true.
Related
I have an application running in a k8s cluster in AzureChinaCloud behind an ingress (internal load balancer) which in turn sits behind an application gateway with a public ip. The DNS point the URL to the public ip and all nslookups are giving back the correct address. The endpoint is HTTPS and the certificate is good and in date and correctly configured on the listener of the application gateway.
However 9 times out of 10 when I try the URL I am getting the below error
"Secure Connection Failed
An error occurred during a connection to blablabla SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified."
However intermittently it does load okay. I cant match the failure timestamps with any failed requests in the app gateway logs. I ran a wireshark and I am seeing some errors like
[TCP Out-of-Order]
I see some RST messages from the client to the server
I also see some HTTP/1.1 403 Forbidden messages but I see some of these during the successful attempts also
If you create a website in china cloud you apparently need to register it with ICP. Below are the details I got from Azure support
Problem Reason:
There seems to be an issue with ICP registration.
More details about ICP registration:
According to the ICP filling requirements of China's Ministry of Industry and Information
Technology (MIIT) and China Public Security Ministry, a website is accessible only if the registration is completed and the filled information is accurate.
In addition, the access should be suspended if any prohibited content is published or disseminated.
If the website has not bound a custom domain, please bind your own custom domain with ICP filing for your websit
So I have been running into this issue since we set up our BizTalk Server on a new network. We have the same MSMQ settings between the two servers.
The data stays in our AX MSMQ folders and has the correct permissions.
The system does not ever throw an error until I stop/restart the Receive Host Instances.
(we get one of these errors per message in any of our MSMQ ports)
Full error:
A message received by adapter "MSMQ" on receive location
"recv_loc_file_ax_2012_customer_message" with URI
"FORMATNAME:DIRECT=OS:AXSERVER\AXOUTPPDCUSTOMER" is suspended. Error
details: The Messaging Engine is shutting down. MessageId:
{65E24FE1-317E-4636-AFC7-B43FACBDBEDF} InstanceID:
{6618EEB3-9B72-4123-BD8C-422661A59BDD}
Then the messages finally appear under suspended instances after this error occurs. I am able to resume them and they all process as expected.
I have looked almost every, Anyone have suggestions for what is causing these messages to not be read into my MSMQ receive ports properly?
EDIT: This BizTalk server is connecting to a remote AX server's MSMQ, but I am doubting this changes anything I have not already looked into.
Thank you very much.
The error was on the guys who installed MSMQ on the remote server; the active directory was not set up thus not properly autenticating my BizTalk Server account.
Answer for BizTalk: The way to find these hidden errors was by changing the MSMQ BizTalk receive port to a WFC-NetMSMQ.
Other: we are a little baffled that BizTalk was able to take the messages out of MSMQ despite the AD not being set up and "force messages through" but this is a minor detail to note.
BizTalk reference
I am having some issues trying to make an AIR application connect to a RemoteObject when the application is run in a domain that has proxy servers for outbound connection.
The error provided is as below:
[RPC Fault faultString="Send failed" faultCode="Client.Error.MessageSend" faultDetail="Channel.Connect.Failed error NetConnection.Call.Failed: HTTP: Failed: url: 'http://myTestService.org:8080/default/message/amf'"]
Any ideas? I think the proxy server may be preventing the application from accessing the Remote Object. How do I work around this?
Thanks.
Edit:
I saw a quite similar post to this:
Remoting with AIR
And I did declared the endpoint and destination to my RemoteObject.
In application/WEB-INF/flex/services-config.xml give only relative paths, do not use ip address and port number. You can look here for detail moving to production server
And here send failed error
In your case channel url should be
"/default/message/amf"
Drupal RPC Fault looks to be some what same as your problem and has issues with crossdomain.xml
Do check it.
In Microsoft BizTalk Application when exception occurred then Services or port will goes to in suspended mode and need to manually start application or port.
What i want is when any exceptions occurred during message processing should send one email alert to system administrator and details of exception should be stored in separate database for further process.
Anyone have any better suggestion how we can do it.
Regards,
Rakesh
To handle the message failure secnario see using Failed Message Routing. As far as monitoring ports when they shut down you can either use MOM (expensive) or write a script to do what you want. There are many posts here in stackoverflow that address this... here is one such post.
To get an email alert sent for any messaging failures (i.e., a failure in a send or receive port)
For each send or receive port for which you want to track failures, edit the port properties and check the box for "Enable routing for failed messages"
For send ports, you'll find this option under "Transport Advanced Options".
The option for receive ports is under the General section of the port properties.
Create a new Send Port (perhaps in a separate "Exception Handling" BizTalk application) that uses the SMTP adapter to send the emails.
To send out all failed messages using this new port, create a filter on the send port with the Property ErrorReport.ErrorType == FailedMessage. That will evaluate as true for all messages that error on a send or receive port for which you enabled Failed Message Routing.
If you need to route messages differently, at a more granular level, then have a look at the properties on the Failed Message Routing page referenced by ChrisLoris.
To track exceptions for failed messages in a separate database, I would start with the Microsoft BizTalk ESB Toolkit Exception Management Framework, as it includes a database for this purpose and the mechanism to push exception/failed message data into that database (build atop Failed Message Routing). It even includes a web site to enable users to interact with the failed messages, which you can customize as you see fit or throw away altogether.
The instructions to install the just the Exception Management part of the ESB Toolkit are available at http://msdn.microsoft.com/en-us/library/ee250099.aspx. Microsoft's guide to using the ESB Exception Management is worth a review too and is here.
A client of our has recently upgraded a ASP.NET 1.1 web application to ASP.NET that uses COM+ transaction processing and received the following exception while trying to process a transaction:
Exception Type:
System.Transactions.TransactionManagerCommunicationException
Message: Communication with the
underlying transaction manager has
failed.
Inner Exception Type:
System.Runtime.InteropServices.COMException
ErrorCode: -2147467259
Message: Error
HRESULT E_FAIL has been returned from
a call to a COM component.
Here are the following settings on MSDTC Security Settings:
-- Network DTC Access
-- Allow Inbound
-- Allow Outbound
-- Incoming Caller Authenication Required
A Windows XP SP3 workstation is trying to establish a connection to a Windows Server 2003 machine.
Has anyone else experienced this error and know how to resolve it.
You'll need to have network DTC access enabled on both your XP workstation and your windows 2003 machine. Also, if your application is only published internally, you can turn off incoming caller authentication and set it to "no authentication".
Add C:\Windows\msdtc.exe to the firewall exceptions on both the firewall and server. I spent ages monkeying around opening specific port numbers and ranges to no avail before I did this.
1)Disable authentication besides enabling the network access to "distributed transaction co-ordination " service
(mutual authentication doesn’t work as displayed in internet in xp sp3 machines)
2) enable network access in client ( web applicaton ) and server ( sql server ) machines for "distributed transaction co-ordination " service .
You'll also need to make sure your firewall is open for ports 135 and 5000-5020.
See these:
http://social.msdn.microsoft.com/forums/en-US/windowstransactionsprogramming/thread/71f7a219-c85d-4a04-973b-c73464f59606/
http://blogs.msdn.com/florinlazar/archive/2005/09/16/469064.aspx
http://social.msdn.microsoft.com/forums/en-US/architecturegeneral/thread/7731d7a7-a9ad-42e7-b0bb-f3656b870304/
http://support.microsoft.com/kb/154596/
In case you need help finding the MSDTC settings mentioned in the other answers (like I did), the following link explains how to configure MSDTC on server 2003.
http://itknowledgeexchange.techtarget.com/sql-server/how-to-configure-dtc-on-windows-2003/