EventViewer error - 1004- UserData does not exist

S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
S

Scott Stanko

Hi,

Thanks for the update. We did find something else after doing some more
testing yesterday. (Well, two things, actually)

The first thing: If we initiated the installation using GPO and "pushed" the
upgrade on a computer specific group, we did not see the problem. The user
logged in and Outlook completed the installation and launched. However, if we
ran the upgrade (batch file with the same transform and mst used in the GPO
Push) locally on the workstation as an admin account and then logged back in
as the user, we got the Outlook error.

The second thing: In order to "fix" the installation for the affected user
account, we just had to nuke their outlook profile and then relaunch outlook
and rebuild it. Not what I really want to have to do, but it's alot easier
than uninstalling and reinstalling the Office Suite.

Hope this helps ... but I wish Microsoft would come up with a permanent fix.
Especially since it seems this problem has been around for while.

Thanks all.
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 
F

Fahrer Gefunden

Hi Scott,

I used setup with an MST template in a batch file, I have not tried the
"push" feature. I too wish the MS would fix this as many people seem to have
this same issue.

THANKS!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

ODBC error 100 when accessing Bookkeeper version 15 software (accounting software using Access dbase) 0
Outlook 2003 - Fails to run - "resource 'UserData' does not exist" 0
Installer error 0
userdata does not exist 0
My computer will print from ALL other programs except MS publisher 2007 4
Upgrade Office XP to 2003 error 0
UserData Registry Key Missing 6
Warning ID 1004 1

Top