cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
285
Views
0
Helpful
5
Replies

Can't register due to incomplete address

I'm trying to register for Cisco Smart Net Total Care Portal following the guide at Cisco Smart Net Total Care Portal Onboarding Guide - Cisco. I'm getting the error my address is incomplete and I should fill it in my account page.

On my account page all fields are filled, I even filled the preferred first name, just to be sure.

Address details are coming from the partner I work for, I went to partner self service and filled in all fields. Just to be sure, I also filled the CSCO number as I just changed employers and it wasn't filled in yet here. All address lines for the partner are filled except Business Address 2 and 3.

So why does the portal say I don't have a complete address when all mandatory fields are filled?

5 Replies 5

adias
Cisco Employee
Cisco Employee

to register for SNTC portal for a company your cco profile must be of that company , are you trying to register for an END user it seems you are a partner.

I have tried to get a PSS contract, but we were too small for that. So now I'm trying to register as an end user on our own company.
Other coworkers can do this registration just fine, it just doesn't work for me.

it is unclear to me what you mean by : "Other coworkers can do this registration just fine, it just doesn't work for me".

If your company already has a SNTC  portal account and other users are in it, you do not register another instance .  the DA of that instance should add you as a user to that portal.

send me a private message with your cco and a cco of a colleage that has access to SNTC portal .

 

I have sent a PM the same day with my CCOID and the CCOIDs of 3 coworkers who can continue with the registration. So far, no response. We have paid smartnets, why is it so hard to get access to the EoX APIs?

Solved: SNTC portal registration error wieth the complete address - Cisco Community

This person had the same issue, there could be a different root cause, but I would appreciate it if someone from Cisco could look into this.