A
andy.novak
Has anyone experience problems after turning on password protection
for source code viewing (via VB editor) in the "checked out
enterprise global" VBAProject?
Ever since I did that, I can't publish plans, can't save the eglobal
(says I don't have the right permissions to save), checkins don't
work. I basically have an unusable system.
Microsoft believes selecting that option in the VB editor at the
eglobal level shouldn't wreck the system. Their tech actually tried
the same thing and it worked as expected. So, what I did apparently
wasn't wreckless.
I restored the eglobal from the online archive and restarted Project
Server but that didn't solve the problems. I've yet to bounce the SQL
Server, but Microsoft is now suggesting restoring all 4 Project
Server databases from the last backup but I'd rather not have to do
that.
I would appreciate any and all suggestions as to the probable cause
and quick remedy.
Thanks,
Andy Novak
UNT
for source code viewing (via VB editor) in the "checked out
enterprise global" VBAProject?
Ever since I did that, I can't publish plans, can't save the eglobal
(says I don't have the right permissions to save), checkins don't
work. I basically have an unusable system.
Microsoft believes selecting that option in the VB editor at the
eglobal level shouldn't wreck the system. Their tech actually tried
the same thing and it worked as expected. So, what I did apparently
wasn't wreckless.
I restored the eglobal from the online archive and restarted Project
Server but that didn't solve the problems. I've yet to bounce the SQL
Server, but Microsoft is now suggesting restoring all 4 Project
Server databases from the last backup but I'd rather not have to do
that.
I would appreciate any and all suggestions as to the probable cause
and quick remedy.
Thanks,
Andy Novak
UNT