MapPoint 2006 registry error

  • Thread starter Thread starter Lonny
  • Start date Start date
L

Lonny

I'm running Vista RC1 and MapPoint 2006 has been running flawlessly for six
weeks or so until the other morning when I got an error message that says,
"Your registry settings for this application were not copied correctly. To
correct these settings, run Setup again for this application from the
location where you originally installed it." Of course, I've done that to
no avail. Did some research on TechNet that pointed to an unholy alliance
with MS Works (which I don't have) and MS Money (which I do) so I followed
those procedures and still no luck.

Now this is really weird! At the suggestion of a friend I installed
MapPoint with UAC turned off. Everything is right with the world. Being
the responsible end user I am (don't laugh, it's true!) I re-enabled UAC and
BOOM! no MapPoint. Just to confirm my suspicions, I disabled UAC and now
MapPoint works.

What's really got me scratching my head is that I've been using MapPoint
2006 for several weeks with UAC turned on and there were no problems. I
really don't want to disable the best protection I have against the dirt
bags of the online world! What might make MapPoint 2006 behave this way?!?

Ideas? Suggestions? Alternative Procedures?

Thanx, ;-)

Lonny
 
Sounds like a bug with MapPoint. Check to see if you Windows Vista is
virtualizing any files or registry entries. to check look in the virtual
store for file look C:\users\[logonid]\appdata\local\virtualStore

and to see reg virts look here.

HKey Classes root\VirtualStore

The simple answer is probably just right click and "run as administrator" on
the map point icon. If that works then you could permantly change that icon
by right clicking and selecting properties and changing how it is run.

you can also create an app compat shim....
 
Okay, I'll give that a try. But why would this behavior start after a
relatively extended period of correct operation? I can't say that nothing
changed (my computer is in a constant state of flux!) but I can't see what
would have modified the behavior of the system to the point where a specific
application would suddenly start behaving badly. :(

Lonny

Josh said:
Sounds like a bug with MapPoint. Check to see if you Windows Vista is
virtualizing any files or registry entries. to check look in the virtual
store for file look C:\users\[logonid]\appdata\local\virtualStore

and to see reg virts look here.

HKey Classes root\VirtualStore

The simple answer is probably just right click and "run as administrator"
on the map point icon. If that works then you could permantly change that
icon by right clicking and selecting properties and changing how it is
run.

you can also create an app compat shim....

--
Josh
http://windowsconnected.com
Lonny said:
I'm running Vista RC1 and MapPoint 2006 has been running flawlessly for
six weeks or so until the other morning when I got an error message that
says, "Your registry settings for this application were not copied
correctly. To correct these settings, run Setup again for this
application from the location where you originally installed it." Of
course, I've done that to no avail. Did some research on TechNet that
pointed to an unholy alliance with MS Works (which I don't have) and MS
Money (which I do) so I followed those procedures and still no luck.

Now this is really weird! At the suggestion of a friend I installed
MapPoint with UAC turned off. Everything is right with the world. Being
the responsible end user I am (don't laugh, it's true!) I re-enabled UAC
and BOOM! no MapPoint. Just to confirm my suspicions, I disabled UAC and
now MapPoint works.

What's really got me scratching my head is that I've been using MapPoint
2006 for several weeks with UAC turned on and there were no problems. I
really don't want to disable the best protection I have against the dirt
bags of the online world! What might make MapPoint 2006 behave this
way?!?

Ideas? Suggestions? Alternative Procedures?

Thanx, ;-)

Lonny
Click to expand...
Click to expand...
 
I am guessing you hit a function of mappoint that was buried and relatively
obsucre? I really don't know since i don't use mappoint.

--
Josh
http://windowsconnected.com
Lonny said:
Okay, I'll give that a try. But why would this behavior start after a
relatively extended period of correct operation? I can't say that nothing
changed (my computer is in a constant state of flux!) but I can't see what
would have modified the behavior of the system to the point where a
specific application would suddenly start behaving badly. :(

Lonny

Josh said:
Sounds like a bug with MapPoint. Check to see if you Windows Vista is
virtualizing any files or registry entries. to check look in the virtual
store for file look C:\users\[logonid]\appdata\local\virtualStore

and to see reg virts look here.

HKey Classes root\VirtualStore

The simple answer is probably just right click and "run as administrator"
on the map point icon. If that works then you could permantly change
that icon by right clicking and selecting properties and changing how it
is run.

you can also create an app compat shim....

--
Josh
http://windowsconnected.com
Lonny said:
I'm running Vista RC1 and MapPoint 2006 has been running flawlessly for
six weeks or so until the other morning when I got an error message that
says, "Your registry settings for this application were not copied
correctly. To correct these settings, run Setup again for this
application from the location where you originally installed it." Of
course, I've done that to no avail. Did some research on TechNet that
pointed to an unholy alliance with MS Works (which I don't have) and MS
Money (which I do) so I followed those procedures and still no luck.

Now this is really weird! At the suggestion of a friend I installed
MapPoint with UAC turned off. Everything is right with the world.
Being the responsible end user I am (don't laugh, it's true!) I
re-enabled UAC and BOOM! no MapPoint. Just to confirm my suspicions, I
disabled UAC and now MapPoint works.

What's really got me scratching my head is that I've been using MapPoint
2006 for several weeks with UAC turned on and there were no problems. I
really don't want to disable the best protection I have against the dirt
bags of the online world! What might make MapPoint 2006 behave this
way?!?

Ideas? Suggestions? Alternative Procedures?

Thanx, ;-)

Lonny
Click to expand...
Click to expand...
Click to expand...
 
Lonny said:
I'm running Vista RC1 and MapPoint 2006 has been running flawlessly for
six weeks or so until the other morning when I got an error message that
says, "Your registry settings for this application were not copied
correctly. To correct these settings, run Setup again for this
application from the location where you originally installed it." Of
course, I've done that to no avail. Did some research on TechNet that
pointed to an unholy alliance with MS Works (which I don't have) and MS
Money (which I do) so I followed those procedures and still no luck.

Now this is really weird! At the suggestion of a friend I installed
MapPoint with UAC turned off. Everything is right with the world. Being
the responsible end user I am (don't laugh, it's true!) I re-enabled UAC
and BOOM! no MapPoint. Just to confirm my suspicions, I disabled UAC and
now MapPoint works.

What's really got me scratching my head is that I've been using MapPoint
2006 for several weeks with UAC turned on and there were no problems. I
really don't want to disable the best protection I have against the dirt
bags of the online world! What might make MapPoint 2006 behave this
way?!?

Ideas? Suggestions? Alternative Procedures?

Thanx, ;-)

Lonny
Click to expand...



I was going to install anyway, so I took the time to do it now. Map Point
2006 works fine. The only thing I saw was a flag during installation saying
that I needed ActiveSync 3.7, or later. This may be your problem.

--


Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
Back
Top