{"id":34722,"date":"2024-07-29T09:23:27","date_gmt":"2024-07-29T09:23:27","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sageaccpacerp\/?p=34722"},"modified":"2024-07-29T09:23:28","modified_gmt":"2024-07-29T09:23:28","slug":"invalid-signon-information-error-in-custom-web-api-service-for-sage-300","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sageaccpacerp\/2024\/07\/29\/invalid-signon-information-error-in-custom-web-api-service-for-sage-300\/","title":{"rendered":"Invalid Signon Information error in Custom Web API Service for Sage 300"},"content":{"rendered":"\n

Sage 300<\/a>, a comprehensive enterprise resource planning (ERP) software, has its own inbuilt features and a robust web API that leverages Swagger for seamless integration and enhanced functionality. The Swagger API framework allows developers to easily interact with Sage 300\u2019s for updating and inserting the data, which enables the integration with third-party mod. Sage 300 follows RESTFUL principles and provides clear as well as interactive documentation through Swagger. It also ensures secure and efficient access to some of the features of various modules like General Ledger, Accounts Payable, and Accounts Receivable. This makes it an invaluable tool for businesses aiming to streamline operations and improve data management.<\/p>\n\n\n\n

New Stuff :- <\/em><\/strong>T<\/a>he Growing Power of Payment Solutions in the ERP Market.<\/a><\/p>\n\n\n\n

This blog aims to offer a guide to understanding and resolving the “Invalid Signon Information” error in custom web service APIs for Sage 300.<\/p>\n\n\n\n

When integrating or developing custom web services for Sage 300, you may encounter a scenario where valid Sage 300 credentials are being passed, yet the API response indicates an “Invalid Signon Information” error.<\/p>\n\n\n\n

\"img1\"<\/a><\/center>\n\n\n\n

In such cases, there may be a chance that the service you are running is not in the Sage 300 application pool. If you want to run it in a different application pool, make sure that this new application pool is configured with the same settings as of Sage 300 application pool.<\/p>\n\n\n\n

To do so, follow the steps below:<\/p>\n\n\n\n

    \n
  1. Open IIS Manager<\/strong>: Open Internet Information Services (IIS) Manager on your server. Shortcut \u201cWin+R\u201d enter \u201cinetmgr\u201d and run.<\/li>\n\n\n\n
  2. Locate Application Pools<\/strong>: In the left-hand Connections pane, expand the server node and click on “Application Pools”.<\/li>\n\n\n\n
  3. Identify Sage 300 Application Pool<\/strong>: Find the application pool used by Sage 300.<\/li>\n\n\n\n
  4. Create a New Application Pool<\/strong>: If you need a new application pool, right-click on “Application Pools” and select “Add Application Pool”. Name the new pool \u201cCustom Web API Service\u201d and configure it with the same settings as the Sage 300 application pool, including .NET version and pipeline mode.<\/li>\n<\/ol>\n\n\n\n
    \"img2\"<\/a><\/center>\n\n\n\n
      \n
    1. Configure the New Application Pool<\/strong>: Set the same identity for the new application pool as the Sage 300 application pool. This can be done by:\n