Picture Manager 2003 - Users unable to edit after upgrade from Office XP

[Guest]

After upgrading everyone from Office XP to Office 2003,
certain people using Picture Manager 2003 are unable to
edit pictures. It works fine for administrators,
suggesting a possible permissions issue, but on a test
system after giving permissions to basically the entire
c:\ drive & entire registry, still no go for user.

I've narrowed it down somewhat. It works fine on systems
that have been loaded from scratch, or on any system that
user hasn't logged into before, therefore creating a new
windows profile when they log in the first time. However,
on one problem system I removed the user's profile, and
had them login again to create a new one, but still had
same problem. Also, removed office 2003 completely and
reinstalled, still no luck.

I am at a loss on this one. Any help would be appreciated

 

[Paul Francis]

I have the same problem. The PCs we have the problem
with have had Office 2000 removed before 2003 was
installed.

Will keep you posted if I find out anything.

 

[Paul Francis]

Found a fix that works for me.

MS Base Article: 828386

Basically - move Internet Explorer Temp files to a
location the user can update.

 

[Jeff Vandervoort]

--

Jeff Vandervoort
JRVsystems
http://jrvsystems.com

 

[Jeff Vandervoort]

Same Picture Manager issue here, but it's not permissions-related. In fact,
I'm currently stumped as to what it's related to:

On one computer, User A can't edit images with PM. User B logs on to same
computer, with identical group memberships, and PM works normally.

User A logs on at another Office 2003 PC (we use roaming profiles, so
profile is the same on both machines) and PM works normally.

Both machines are Win2K SP4. Both were upgrades over Office 2K SP1 installed
by GPO with the same MST and same RSOP.

User has normal (Full Control) permissions on the Temporary Internet Files
folder, so that's not it either.

Detect and Repair didn't help.

FWIW, I use PM successfully on 3 different PCs while having only "User"
group membership.

I'd sure like to get to the bottom of it before rolling this out to the rest
of the company, but no idea where to look next.

 

[Jeff Vandervoort]

More info...

I deleted User A's profile from the computer on which she could not edit
images and let Windows set her up as a new user, downloading her profile
from the profile share on the server. That should have duplicated the
condition on the other Office 2003 PC where she did not have an existing
profile, but could edit with PM.

She still can't edit with PM on her computer.

 

[Pascal]

Hello,

Exactely same problem here : ok when admin, doesn't work when user
Think we need a quick answer from Microsoft Support guys ^^

 

[Pascal]

Just found a "turn-arround" solution : "irfanview" , a freeware. Works fine. Powered tools

 

[btushaus]

I was struggling with the exact same problem that this post describes.
I nearly pulled my hair out trying to figure out what was going on.
Nothing made sense. I finally found that if the computer name and th
logged on user name were the same, the problem of not being able t
edit a picture in Picture Manager would occur. As soon as I rename
the computer to something other than the user's name or I logged tha
same user (with a roaming profile) on to a different computer (with
different name) the problem would go away and Picture Manager woul
work properly. I can't say that I figured out why it does this but a
least now I know the cause and I can work my way around it. I hop
this helps some of you others.

*Same Picture Manager issue here, but it's not permissions-related
In fact,
I'm currently stumped as to what it's related to:

On one computer, User A can't edit images with PM. User B logs on t
same
computer, with identical group memberships, and PM works normally.

User A logs on at another Office 2003 PC (we use roaming profiles
so
profile is the same on both machines) and PM works normally.

Both machines are Win2K SP4. Both were upgrades over Office 2K SP
installed
by GPO with the same MST and same RSOP.

User has normal (Full Control) permissions on the Temporary Interne
Files
folder, so that's not it either.

Detect and Repair didn't help.

FWIW, I use PM successfully on 3 different PCs while having onl
"User"
group membership.

I'd sure like to get to the bottom of it before rolling this out t
the rest
of the company, but no idea where to look next.

--

Jeff Vandervoort
JRVsystems
http://jrvsystems.com
message

-
btushau