Hi @bala,
The error message you provided states: “An unexpected error has occurred. Please try again by launching the app installed on your site.” This is not the expected behavior after successfully onboarding the O365 application. Typically, you should be able to access the application without errors.
Here are some steps you can take to investigate and resolve the issue:
Check the URL and Application Path:
Review the Web.Config File:
- Open the web.config file for your O365 application.
- Look for any configuration settings related to authentication, authorization, or routing.
- Ensure that the settings are correctly configured for your application.
Custom Errors Mode:
- To get more detailed error information, temporarily set the custom errors mode to “Off” in the web.config file:
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
#Analyzing the provided log entries:
1. **2024-02-23 06:01:23**:
- Two requests were made simultaneously, one from IP address 192.A.B.C and the other from 192.A.B.D.
- Both requests returned a status code of 200.
- The time taken to process the requests was 2 milliseconds for the first request and 1 millisecond for the second.
2. **2024-02-23 06:01:53**:
- Similar to the previous instance, two requests were made simultaneously from IP addresses 192.A.B.C and 192.A.B.D.
- Both requests returned a status code of 200.
- The time taken to process the requests was 1 millisecond for the first request and 2 milliseconds for the second.
3. **2024-02-23 06:02:23** - **2024-02-23 06:03:53**:
- Similar patterns continue with alternating requests from IP addresses 192.A.B.C and 192.A.B.C
- The status codes remain 200 for all requests, with varying processing times.
4. **2024-02-23 06:05:18**:
- An additional request is made from localhost (127.w.w.2), which appears to be accessing the server.
- The user-agent string indicates it's a request made by a browser, possibly Chrome or Edge, running on Windows 10.0.
- The status code is 200, and the processing time is 1 millisecond.
5. **2024-02-23 06:06:23** - **2024-02-23 06:06:53**:
- Unusually high processing times are observed for these requests, 168 milliseconds and 411 milliseconds, respectively.
6. **2024-02-23 06:08:23**:
- Another unusual occurrence with processing times of 401 milliseconds and 182 milliseconds for requests from IP addresses 192.A.B.C and 192.A.B.D, respectively.
7. **2024-02-23 06:10:04**:
- Similar to the previous localhost request, another request is made, and it's likely from the same source.
- The status code is 200, and the processing time is 3 milliseconds.
8. **2024-02-23 06:10:53**:
- This entry shows an unusually high processing time of 6 milliseconds for a request from IP address 192.A.B.C.
Overall, the log shows a series of GET requests made to the server with alternating IPs, generally returning a status code of 200 with varying processing times. There are a few instances of unusually high processing times,But there is no error in the logs.
For further insights and troubleshooting assistance, I encourage you to refer to the documentation and forum posts provided below:
Link 1: IIS Installation for O365 Onboarding
Link 2: IIS Server O365 Agent Questions for O365 Integration
Link 3: Using Classic Integration
Link 4: Integrating Microsoft Office 365 Applications
Second Link:-(https://docs.saviyntcloud.com/bundle/MSOffice365-v23x/page/Content/Using-Application-Integration-v20...)
Link 5: Office 365 Test Connection
Link 6: Troubleshooting
Link 7: Understanding the Integration between EIC and Windows Server
Please review the provided resources and reach out if further assistance is needed. Thank you for your cooperation and patience.
