PowerSchool SIS Wisconsin
PowerSchool SIS Wisconsin
Breadcrumbs

Common WI Ed-Fi Errors

Error

Response

WISE ID

Cannot auto assign student unique id. Id: xxx Error: UniqueIDService UniqueidService REST error. Provider Error Message: Message: Invalid response from identify service: The ApiKey ‘Powerschool – xxx” is not authorized to send EducationOrganizationid: xxx”… The ApiKey ‘Powerschool – xxx” is authorized for the following xxx.

Solution: Update District Info > Ed-Fi State LEA Number to the number provided in the returned error message.

Setup:

Test Connection > Successful
Used Student Number xxxxx

Error:
Cannot auto assign student unique id. Id: xxx. Error: UniqueIdService UniqueIdService REST error. Provider Error Message: Message: Invalid response from identity service: The ApiKey 'PowerSchoolSIS_2026_xxxx_myschoolc' is not authorized to send EducationOrganizationId: 8032. The ApiKey 'PowerSchoolSIS_2026_xxxx_myschoolc' is authorized for the following EducationOrganizationId(s) (xxxx)... Exception Message: . Exception Type: See database log for details.
Diagnostic Viewer
Error Code: 502. Message: Cannot auto assign student unique id. Id: 111. Error: UniqueIdService UniqueIdService REST error. Provider Error Message: Message: Invalid response from identity service: ..

Solution: This is a setup issue caused by an incorrect LEA number. Navigate to the District Setup page and modify the LEA from 8032 to xxxx found in the key.

Setup: SubDistrict

Bad Authentication Key and/or Secret

Solution:

  1. Copy the Sub-District's previous (if applicable) and current Key & Secret

  2. Remove the school from the Sub-District configuration and re-added them.

  3. Confirm that a successful connection for both the previous and current Test Connection.

Stuck in publishing? - SubDistricts in Use-

Solution:
Data Exchange > General Setup -> Test Connection (must test all active subdistricts)

Remove the key and secret for the disabled Sub-District(s)

  1. Diag Viewer: Pending Jobs Publishing > First record is the record in error > What profile is it linked to and what school year; If the profile/school year is shut off then this will cause the rest to get stuck; Can run special ops to clear the records for the disabled school;
    or

  2. Turn off data exchange and then turn it back on (top of General Setup page);

Unable to reconcile student who should not have data published.  Student is marked to be excluded and have tried deleting the Published records but they continue to come back.

Solution:

This typically happens when a vendor is publishing the student's special education program.  Client must first remove the published special education program from the vendors application, then they can complete the reconciliation process in PowerSchool.