Office error: “We weren't able to register your device and add your account to Windows.”
up vote
0
down vote
favorite
Full error
Something went wrong
We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.
History
Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.
After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.
Question
How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?
windows-10 office365
edited Aug 29 at 18:23
harrymc
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
|
show 2 more comments
up vote
0
down vote
favorite
Full error
Something went wrong
We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.
History
Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.
After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.
Question
How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?
windows-10 office365
edited Aug 29 at 18:23
harrymc
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
1
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
1
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39
|
show 2 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Full error
Something went wrong
We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.
History
Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.
After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.
Question
How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?
windows-10 office365
edited Aug 29 at 18:23
harrymc
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
Full error
Something went wrong
We weren't able to register your device and add your account to
Windows. Your access to org resources may be limited.
History
Due to a local domain issue, I had to remove my PC from the domain and re-add it. After that my user profile was broken so I used a tool to migrate it. Upon logging in, all my settings were back but I was not logged into my Office 365 apps. When I try to, I get the error above.
After lots of troubleshooting, I created a new local account on my PC and was able to successfully set up Office and login as expected.
Question
How can I fix my current domain-based Windows profile so that I can login to Office using my Office365 credentials?
windows-10 office365
windows-10 office365
edited Aug 29 at 18:23
harrymc
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
edited Aug 29 at 18:23
harrymc
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
edited Aug 29 at 18:23
harrymc
247k10256542
edited Aug 29 at 18:23
harrymc
247k10256542
edited Aug 29 at 18:23
harrymc
247k10256542
247k10256542
asked Aug 29 at 17:58
Scott Beeson
58952053
asked Aug 29 at 17:58
Scott Beeson
58952053
asked Aug 29 at 17:58
Scott Beeson
58952053
58952053
1
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
1
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39
|
show 2 more comments
1
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
1
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39
1
1
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
1
1
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39
|
show 2 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus
Take note of the last 5 digits of the product key. Then run this command:
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX
(replace the XXXX with the last 5 chars of the prod key):
This is only recommended for users who have Office Apps with Office 365 license.
Reference here
edited Nov 13 at 16:34
Mr Shunz
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus
Take note of the last 5 digits of the product key. Then run this command:
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX
(replace the XXXX with the last 5 chars of the prod key):
This is only recommended for users who have Office Apps with Office 365 license.
Reference here
edited Nov 13 at 16:34
Mr Shunz
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus
Take note of the last 5 digits of the product key. Then run this command:
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX
(replace the XXXX with the last 5 chars of the prod key):
This is only recommended for users who have Office Apps with Office 365 license.
Reference here
edited Nov 13 at 16:34
Mr Shunz
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
up vote
0
down vote
I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus
Take note of the last 5 digits of the product key. Then run this command:
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX
(replace the XXXX with the last 5 chars of the prod key):
This is only recommended for users who have Office Apps with Office 365 license.
Reference here
edited Nov 13 at 16:34
Mr Shunz
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I know this is an old post but this might help someone out there.
I forgot I had an existing installation of Office 365 and I keep getting the above error. I ran these commands in CMD (open as admin):
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /dstatus
Take note of the last 5 digits of the product key. Then run this command:
cscript.exe "%ProgramFiles(x86)%Microsoft OfficeOffice16ospp.vbs" /unpkey:XXXX
(replace the XXXX with the last 5 chars of the prod key):
This is only recommended for users who have Office Apps with Office 365 license.
Reference here
edited Nov 13 at 16:34
Mr Shunz
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited Nov 13 at 16:34
Mr Shunz
1,6301516
edited Nov 13 at 16:34
Mr Shunz
1,6301516
edited Nov 13 at 16:34
Mr Shunz
1,6301516
1,6301516
answered Nov 13 at 14:47
SavageTofu
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered Nov 13 at 14:47
SavageTofu
1
answered Nov 13 at 14:47
SavageTofu
1
1
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
SavageTofu is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1353510%2foffice-error-we-werent-able-to-register-your-device-and-add-your-account-to-w%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
There are certain limitations to Volume License activation, in particular, the number of activations that must happen at once. Contact your network administrator for assistance.
– Ramhound
Aug 29 at 18:23
Why was I able to "activate" it under a new local profile? I don't think this is a licensing thing...
– Scott Beeson
Aug 29 at 18:26
Is your situation the one solved in the last entry on this post?
– harrymc
Aug 29 at 18:35
No, that mentions a "DatabaseNotFoundException" error which I don't get. Also, the fix is to login to outlook.live.com which I cannot do with an Office365 account. That problem is in no way related to this as far as I can tell.
– Scott Beeson
Aug 29 at 18:36
1
@ScottBeeson - Likely due to the fact the group policy was applied to the machine. You certainly can log into outlook.live.com with an Office 365 account. Both are Microsoft accounts (not saying it will fix anything though)
– Ramhound
Aug 29 at 20:39