nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Lost Connectivity to test environment after Database refresh

Wendy Sporleder

Blackbaud customer had test environment refreshed ahead of GoLive and application will not connect. Application is still listed and connected on BB Customer side and new token did not fix the problem.

Calling SKY API for records to sync from RE NXT: Start date 12/7/2020 12:00:00 AM.
Error in Builder.NextPage(): One or more errors occurred.. System.Exception: RE SKY API error in ApiClient.ExecuteGetRequest(): Error code 'Forbidden' when executing command https://api.sky.blackbaud.com/constituent/V1/constituents?last_modified=12/7/2020&limit=5000&include_deceased=true&include_inactive=false&sort=id: 'Forbidden'.
at TAMRetail.Integration.Blackbaud.SkyAPI.ApiClient.<ExecuteGetRequest>d__18.MoveNext() in

\\TAMLibraries\\V12.1\\Integration\\Blackbaud\\TAMRetail.Integration.Blackbaud\\SkyAPI\\ApiClient.cs:line 144. Stack:    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
   at System.Threading.Tasks.Task`1.get_Result()
   at TAMRetail.Integration.Blackbaud.Builder.Builder.NextPage() in

\\TAMLibraries\\V12.1\\Integration\\Blackbaud\\TAMRetail.Integration.Blackbaud\\SkyAPI\\Builder.cs:line 78

Find more posts tagged with

Comments

Ben Wong

Hi Wendy Sporleder‍,

A couple of things to check:

1. Make sure your application is connected to the right environment

2. Make sure the user who is authorizing the app has the required permission level in the Blackbaud environment/solution

If you'd like me to look up specific application or environment IDs, feel free to send me a message.

Hope that helps!

Wendy Sporleder

Thank you, Ben. As it turned out I created the RE security records in our test environment instance so when we refreshed from production, those were not there and as a result the developers did not have access to the database. Once this was recreated, they also had to re-authorize and refresh the app token and were then able to get to the data. Good to know for our migration to production on Monday!