The request failed with HTTP status 405: Method Not Allowed

The request failed with HTTP status 405: Method Not Allowed

HTTP Error 404.17 - Not Found
The requested content appears to be script and will not be served by the static file handler.



Just Select .asmx and click "Revert to Inherit" to solve the problem



Comments

Post a Comment

Popular posts from this blog

This transaction has been marked for settlement by another user in AX 2009 / 2012

Image
“I need to settle a customer (or vendor) transaction but when I go to the ‘Settle open transactions’ form for the customer (or vendor), I cannot mark the transaction. There is a red icon in the ‘Is marked’ field and I receive an error if I try to mark. I’ve looked all over and I cannot find where to unmark it." Solution When this happens, the user has generally already done their due diligence and checked the likely places to find where the transaction may be marked – in other journals of the same type, in the Settle open transactions form, etc. and still cannot find where it is mysteriously marked. To find where the transaction is marked, take the following steps: 1. Go to Accounts receivable-> Common-> Customers-> All customers-> highlight customer-> Collect tab-> Settle open transactions (similar path for Vendor transactions). Normally you will see the transaction still has the red icon indicating the transaction is still marked elsewhere. 2. Highlight the rec...
Read more

Move AR Records from History to Open - Reversing Apply ( After Paid Transactions Removal )

Move AR Records from History to Open - Reversing Apply ( After Paid Transactions Removal ) The apply process in Dynamics GP is different between the receivable and the payable modules, when payable transactions are fully applied they are "automatically" moved to history which means that the data is migrated from the open tables into the history tables. On the other hand, this is not the same behavior of the receivable module, in which fully applied documents are not moved to history at all unless a specific routine in the system which is called "Paid Transactions Removal" is run, upon which, the documents are moved from the open table to history.  Apply Reversal Due to the different behavior of the modules illustrated above, AR transactions can be applied and un-applied at any time provided that the "paid transaction removal" process is not run. On the other hand, this is not the case in the payable module, because historical transactions...
Read more

Production has work center assigned in its production route that belongs to different sites

The error "Production has work center assigned in its production route that belongs to different sites" in Microsoft Dynamics AX 2009 typically occurs when a work center in a production route is assigned to a different site than the production order's assigned site. To resolve this issue, follow these steps: Step 1: Verify Production Route Setup Go to the production order where you're encountering the error. Path: Production Control > Common > Production orders > All production orders . Open the production order and navigate to the Route tab. Review the work center (Resource) assigned in each operation of the production route. Confirm that the work centers are assigned to the same site as the production order. Step 2: Check Work Center Site Assignment Go to the Work Centers (Resources) in the setup. Path: Basic > Common Forms > Resources > Work Centers (or similar depending on your module configuration). Find the work centers used in the prod...
Read more