Click HERE to see how Saviynt Intelligence is transforming the industry. |
02/09/2024 12:07 AM
Hi Team,
After we followed all the steps to onboard the O365 application, when we try to hit the O365 application running on IIS Server throws the below error. Is this expected behavior or do we get some other messages?
Thanks.
02/12/2024 09:10 PM
Hi @bala,
We are checking on your issue and we will keep you posted.
02/15/2024 10:43 PM
Hi Team,
Any updates on this please?
02/16/2024 07:14 AM
Hi @bala,
We kindly request additional details regarding the Connector. Specifically, could you provide us with information regarding the errors encountered in the logs? Additionally, we would appreciate knowing which documentation you are following for the steps to onboard the O365 application.
Your prompt response will greatly assist us in addressing any issues effectively. Thank you for your cooperation.
02/22/2024 10:15 PM - edited 02/23/2024 02:21 AM
Hi Team,
Attaching the IIS log file, let me know how to validate the IIS Saviynt app after installation? What will be the validate step provided by Saviynt, like steps we need to do after deploying the app in IIS.
Thanks.
[This message has been edited by moderator to remove attached logs with sensitive info]
02/28/2024 09:51 PM
Hi @bala,
Thanks for the update,I will check the shared details and update you accordingly.
02/29/2024 10:47 PM
Any updates, its been a major blocker now and Saviynt tickets are again routing here on forum for solutions. Can you please help on this?
03/01/2024 12:38 AM - edited 03/01/2024 01:23 AM
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:
a. Microsoft 365 Agent URL: This consists of the IIS server IP or hostname along with the port number where Agent Site has been configured in the IIS Manager.
Review the Web.Config File:
Custom Errors Mode:
<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 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.
03/10/2024 11:42 PM
Hi,
Tried all the above possible solutions, can you paste the o365 connector app success redirect page? Just want to know screenshot of success app loading page, since its not mentioned in any Saviynt documents.
If I don't see any errors in IIS logs since all are 200 success messages, I feel its not IIS config issues. Attaching the logs for reference.
While running regular access import it throws below error. While running access detail Job no error and nothing pulled in Saviynt.
Is it DAG license limitation issues? Let me know if any details needed to sort this issue? I can share it. Thanks.
Job Type | full |
Import Type | access |
Error In callRestWebService WebService call failed 2024 03 02T03 59 35 | Failed-url-https://*******.********.com:*****/api/GetSiteCollections, apiRequestDetails-{"environment":"Online"}, Error-********.*****.com |
isRetriedAPI | true |
isFailedEvent | true |
isFailedAPI | true |
Error WebService call failed After retrying 5 times with responseStatusCode 500 2024 03 02T03 59 45 | Failed url-https://*****-admin.sharepoint.com/_api/web/lists/GetByTitle('DO_NOT_DELETE_SPLIST_TENANTADMIN_AGGREGATED_SITECOLLECTIONS')/items?$filter=ID%20ge%201%20and%20IsGroupConnected%20eq%201&$OrderBy=ID&$top=1000, apiRequestDetails-{"bodyParamsMap":""} with Error-{"error":{"code":"-2146232832, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"Column 'IsGroupConnected' does not exist. It may have been deleted by another user."}}} |
Entitlements TeamSiteCollections Retrived From Office365 | 0 |
Entitlements SiteCollections Inactivated | 0 |
03/12/2024 02:23 AM
Hi @DixshantValecha ,
Any help on the above error and IIS app issue? Thanks.
Regards,
Balaji Balakrishnan
03/13/2024 08:34 AM
Hi @bala
This message is expected, you can check from save and test connection to see for any issues or use the postman Api from IIS server app.
Thanks
Darshan
03/15/2024 03:52 AM
Hi @Darshanjain ,
Can you paste the IIS O365 connector app success redirect page here?
Can you be more clear what you're rereferring to "This message is expected" Is the IIS app UI error "An unexpected error has occurred" or the error "
Failed url-https://*****-admin.sharepoint.com/_api/web/lists/GetByTitle('DO_NOT_DELETE_SPLIST_TENANTADMIN_AGGREGATED_SITECOLLECTIONS')/items?$filter=ID%20ge%201%20and%20IsGroupConnected%20eq%201&$OrderBy=ID&$top=1000, apiRequestDetails-{"bodyParamsMap":""} with Error-{"error":{"code":"-2146232832, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"Column 'IsGroupConnected' does not exist. It may have been deleted by another user."}}}" |
Thanks.
03/16/2024 09:03 PM
Hi @DixshantValecha ,
Any update on the above error and IIS app issue? Can you paste the IIS O365 connector app success redirect page here? Thanks.
Regards,
Balaji Balakrishnan
03/18/2024 11:35 PM
Hi @bala,
This issue requires further triage,hence we have rasied a Fresh service ticket for the same.I have messaged you the ticket.Please let me know if further details are needed on this.