Topics Map > Service Information

MyUW - Error Codes

Soon Universities of Wisconsin employees will notice a different look when accessing my.wisconsin.edu.
This change will not apply to UW-Madison or Flex employees.

Instead of reaching the MyUW portal, you'll use the new HRS and Campus Dashboard. For more information about this transition, check out the HR, Payroll and Benefits News announcement.

Index of defined MyUW error codes with supporting information.

Defined MyUW error codes

MYUW-001

MYUW-001 arises when MyUW expects but does not receive an HRS emplid for a user among the user attributes MyUW receives when the user logs into MyUW. This might be because the user does not have an identity in HRS at all. Or it might be because that HRS identity is not fully linked with the credentials (username and password) the user logged in with.

This error specifically means that MyUW did not receive the HRS emplid. MyUW cannot use identity information it does not receive. If the user has an HRS emplid and should have access to HRS integration via MyUW, then the problem in identity linking will need to be resolved by their identity provider (the campus providing their identity).

MYUW-002

MYUW-002 arises in some circumstances when MyUW issues a 403 Forbidden HTTP status code response.

This might mean the user really is not authorized to access whatever path or take whatever action they were trying to take. In this case, trying again with authorizations, authorization rules, and identity unchanged will not help.

Unfortunately, it also might just mean that MyUW got confused about who the user is and what attributes and authorizations they have. This might happen in the case of session expiration or transient failure of server-side modules. In this case, trying again may work around the problem.

Technically, this error specifically means that the root servlet context provided the UI for the 403 Forbidden HTTP response.. Not all applications rely upon the root context to provide this response in all cases, and so there are other 403 status responses that are not this specific case. MYUW-002 in part exists to disambiguate where the 403 status response experience is being generated to support troubleshooting.

MYUW-003

MYUW-003 arises in some circumstances when MyUW issues a 404 NOT FOUND HTTP status code response.

This might mean MyUW could not find whatever path or content the user requested because that content does not exist to find. In this case, trying again will not help.

Unfortunately, it also might just mean that MyUW got confused about who the user is and what attributes and authorizations they have, and so cannot find the requested content given the apparent authorizations of the user. This might happen in the case of session expiration or transient failure of server-side modules. In this case, trying again may work around the problem.

Technically, this error specifically means that the root servlet context provided the UI for the 404 NOT FOUND HTTP response.. Not all applications rely upon the root context to provide this response in all cases, and so there are other 404 status responses that are not this specific case. MYUW-003 in part exists to disambiguate where the 404 status response experience is being generated to support troubleshooting.

MYUW-004

MYUW-004 arises when the MyUW client code running in the user's browser requests the information it needs to render a widget, the server responds with an error, and so the client cannot render the widget. This is typically because the user does not have permission to access the widget (is not in its intended audience) or because the widget has been deleted from the server. Users can lose permissions to widgets through changes in Manifest group memberships, student or employee status, or other changes to their identity. MyUW shows MYUW-004 so that the user has an opportunity to notice that a widget previously in their layout has stopped working and choose to update their layout to remove it, thereby internalizing the change rather than content silently disappearing with no user involvement.

MYUW-005

MYUW-005 arises when Madison users access my.wisconsin.edu. In some cases MyUW is able to detect this and automatically redirect Madison users over to my.wisc.edu. In other cases MyUW is not able to automatically redirect, and instead shows a banner message indicating this error and providing a link to access my.wisc.edu. "Madison users" means users logging in as a Madison-scoped eduPersonPrincipalName (that is, logging in via login.wisc.edu). my.wisc.edu offers Madison users more Madison-specific content than is available in my.wisconsin.edu.

MYUW-006

MYUW-006 arises when a browser makes a request for a MyUW API that expected a logged in user session, but the request is not part of a logged in user session, possibly because the session timed out. Users experiencing this error can log in to MyUW again and then re-try the request. This error is not usually shown to users. Rather, MyUW JSON APIs can give this error. Under some circumstances the MyUW front end running in the user's browser will detect this error and automatically redirect the user through login. This error is technically distinct from MYUW-007 in that the way the user is not logged in is that they are modeled as uPortal's "guest" not-logged-in meta user.

MYUW-007

MYUW-007 arises when a browser makes a request for a MyUW API that expected a logged in user session, but the request is not part of a logged in user session, possibly because the session timed out. Users experiencing this error can log in to MyUW again and then re-try the request. This error is not usually shown to users. Rather, MyUW JSON APIs can give this error. Under some circumstances the MyUW front end running in the user's browser will detect this error and automatically redirect the user through login. This error is technically distinct from MYUW-006 in that the way the user is not logged in is that they are missing a specific uPortal user attribute that should have been populated by the mechanism that binds Shibboleth login data to the user session.

MYUW-008

MYUW-008 arises when the in-browser front end JavaScript application requests some kinds of content from the server and encounters a 403 NOT AUTHORIZED response from the server.

MYUW-009

MYUW-009 arises when the in-browser front end JavaScript application request for the JSON for a widget fails.

MYUW-010

MYUW-010 arises when the in-browser front end JavaScript application request for Portlet markup fails. Technically this error particularly involves the server failing to render a Portlet in "exclusive mode".

MYUW-011

MYUW-011 arises when the user attempts to remove a widget from their layout and the front end is unable to read the title of the widget from the server. This is typically because the widget has been deleted from the server such that the server no longer maintains data about what title was associated with the key for the item. This can also be because the user does not have sufficient permissions to read the data about the widget including its title ("BROWSE" permission on that specific content item). This error isn't intended to prevent the user from removing the widget from their layout and this error code by itself does not indicate that removal was prevented. This error code just indicates that the removal experience was degraded because the front end could not determine the title of the content being removed from the layout.

MYUW-012

MYUW-012 arises when the user's browser presents cookies to MyUW with a total size greater than MyUW's cookie size limit. (That limit is currently 8190 bytes.)

Users can resolve this problem by clearing their browser cookies. They don't have to clear all cookies for everything -- clearing the cookies affecting my.wisc.edu, especially the .wisc.edu domain cookies, will resolve the problem.

The main way this happens is when the user's browser has picked up cookies set at the .wisc.edu domain level (such as Google Analytics cookies and HotJar cookies). Cookies set at the .wisc.edu domain level will be presented to every website within the .wisc.edu domain, including my.wisc.edu, even though most websites will not make use of those cookies. It is a better practice to set cookies more tightly to the specific sub-domain that is setting them and will use them. MyUW sets a MyUW-local limit and presents an error to requests above this limit because cookies growing beyond this limit will eventually hit other limits that cause more confusing errors. By intercepting this problem at this limit, MyUW can provide an error message specific to this issue of excessive cookies.

MYUW-013

MYUW-013 arises when MyUW is unable to load Benefit Enrollment Confirmation Statements.

MYUW-014

MYUW-013 arises when MyUW is unable to load WRS Statements of Benefits.



Keywordsmessage messages code errors MYUW-001 MYUW-002 MYUW-003 troubleshoot troubleshooting MYUW-004 MYUW-005 MYUW-006 MYUW-007 MYUW-008 MYUW-009 MYUW-010   Doc ID114155
OwnerAmanda M.GroupMyUW Madison
Created2021-10-07 08:52:52Updated2024-06-03 15:07:11
SitesDoIT Help Desk, DoIT Staff, My UW-Madison Portal, MyUW System Portal
CleanURLhttps://kb.wisc.edu/myuw/myuw-error-codes
Feedback  1   3