- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-13-2024 01:09 PM
I'm setting up the Solarwinds SGC but running into an error when testing the connection.
Error: com.snc.process_flow.exception.ProcessAutomationException: Error creating Attachment raw_page_stream : Method failed: (/api/now/hub/temporaryattachment) with code: 400 with reason: Attachment is empty
I've read a few posts which mention it being a credential/access/permissions issue on the Solarwinds side but have not seen any specific details on what access needs to be enabled and where.
Does anyone have any suggestions?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2024 06:26 AM
Fixed issue.
This was tied to two primary issues:
1. The port used for Solarwinds has changed in recent years. Port 17778 has been depreciated since 2023 versions of Solarwinds and now uses Port 17774.
2. Issue was tied to credential permissions on the Solarwinds side. I can't confirm the exact permission that was needed but elevating the respective Solarwinds account to admin immediately circumvented the issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2024 07:58 AM
We are having this exact same issue. When we check the outbound HTTP request, it states that it's actually a 404 error. Hoping someone can provide a solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2024 06:26 AM
Hi @LShetler - I have fixed this issue on my end now. See my accepted solution and hopefully it fixes issues for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2024 06:26 AM
Fixed issue.
This was tied to two primary issues:
1. The port used for Solarwinds has changed in recent years. Port 17778 has been depreciated since 2023 versions of Solarwinds and now uses Port 17774.
2. Issue was tied to credential permissions on the Solarwinds side. I can't confirm the exact permission that was needed but elevating the respective Solarwinds account to admin immediately circumvented the issue.