A Power InRoads/Project Defualts Catch 22 Situation

We use ProjectWise at our agency and when an user tries to open a file, he cannot, because it says the Project Preferences (Project Defaults) are not set, but we cannot set them without being able to open Power InRoads. 

It's a Catch 22. 

We can't open Power InRoads because the Project Defaults are not set and we cannot set the Project Defaults because we cannot open Power InRoads.  Any ideas?

Parents
  • Thank you Tom and Caddcop for your replies.

    The problem has been solved.  It turns out I was looking in the wrong place.  I was under the assumption the user was a current user on a new machine, but it turned out he was a New User and needed his profile set up.  As soon as I set him up a profile, Power InRoads opened up.  It did have the Project Defaults set.  This probably happened when we set them by launching Power InRoads outside of ProjectWise.  (We had been under the mistaken belief that even though they were set outside of ProjectWise, they were not setting for Power InRoads when we tried to open a .dgn from ProjectWise.)

    Thank you again,

    Darren

Reply
  • Thank you Tom and Caddcop for your replies.

    The problem has been solved.  It turns out I was looking in the wrong place.  I was under the assumption the user was a current user on a new machine, but it turned out he was a New User and needed his profile set up.  As soon as I set him up a profile, Power InRoads opened up.  It did have the Project Defaults set.  This probably happened when we set them by launching Power InRoads outside of ProjectWise.  (We had been under the mistaken belief that even though they were set outside of ProjectWise, they were not setting for Power InRoads when we tried to open a .dgn from ProjectWise.)

    Thank you again,

    Darren

Children
No Data