What has been your experience with this problem in 2007?
Thank you
OptimumOrg wrote:
I have run into this same problem - we are following a standard code promotion
01-Jun-07
I have run into this same problem - we are following a standard code
promotion practice with global templates in a Project Server 2003
installation. We make changes to the global template in development, save
it, test it, then back it up and restore it to the production environment.
Every time we do this, each custom base calendar gets a '1' added to the end
- and then it deletes the original
For example, we have 'CustomBase' in both environments. We change something
else (say, an Enterprise Outline Code value) in development and save it. We
backup the global template, then restore it to production. After exiting and
restarting Project Pro, we see 'CustomBase1' in production - and we can't
rename it or delete it
We are using the custom calendars as task calendars
Does anyone know if Project Server 2007 also has this bug? Calendars is the
only Organizer object this is happenning with
Thanks
Brian Luca
:
Previous Posts In This Thread:
Calendar won't
MS Project 2003 (11.2.2005.1801.15) SP2 Project Server 2003 SP
When I attempt to delete a calendar using the organizer in the Enterprise
global, I get the message "You cannot change an enterprise base calendar from
here. Check out the enterprise global to rename, edit, or delete enterprise
base calendars." How can I get rid of this calendar? It is not the standard
calendar which I know must stay. I delete it from the enterprise global and
then attempt to delete it from Global (+ non-cached Enterprise) but then get
the message and of course it reappears in the Checked-out Enterprise Global
from the Global. In an attempt to clear this, all projects have been
deleted, however we do have some templates remaining. This is on our test
area we use to do our training
Peggy Cornett
Peggy --Open the Enterprise Global for editing and use the Organizer to delete
Peggy -
Open the Enterprise Global for editing and use the Organizer to delete the
calendar from the Enterprise Global file only. You don't need to delete it
from the Global (+ non-cached Enterprise) file. Close the Organizer and
then save and close the Enterprise Global file. Exit and relaunch Microsoft
Project Professional 2003 and the calendar in question should be gone. Let
us know if this helps
--
Dale A. Howard [MVP
VP of Educational Service
msProjectExpert
http://www.msprojectexperts.co
http://www.projectserverexperts.co
"We write the books on Project Server
What you said is exactly what I thought should happen, but no this calendar
What you said is exactly what I thought should happen, but no this calendar
does not stay away. Again, I opened the Ent Global, organizer, delete the
unwanted calendar from the right side being the ent global, saved and closed
ent global, closed MS Project, relaunched MSP, and went straight to organizer
and there it was back in the ent global. Of course, it is in the drop down
under project information as well. I'm quiet perplexed
Peggy Cornet
:
Peggy --Odd. Is this a custom calendar you created? Or something else?
Peggy -
Odd. Is this a custom calendar you created? Or something else? Let us
know
--
Dale A. Howard [MVP
VP of Educational Service
msProjectExpert
http://www.msprojectexperts.co
http://www.projectserverexperts.co
"We write the books on Project Server
The calendar I can't seem to delete successfully is a custom calendar.
The calendar I cannot seem to delete successfully is a custom calendar. The
are two custom calendar's and of course the standard calendar.
~Peg
:
Re: Calendar won't
Peggy --
Well, I'm drawing a blank. Try this:
1. Launch Project Professional 2003, select the My Computer option, and
then click the Work Offline button.
2. Click Tools - Organizer - Calendars.
3. Look at the list of calendars on the left side of the page (in the
Global.mpt file). Do you see the custom calendar(s) there? If so, delete
them, then click the Close button.
4. Close Project Professional 2003 and then relaunch the software. Connect
to Project Server.
5. Click Tools - Organizer - Calendars. Do you see the custom calendar(s)
there now?
Let us know what you find out.
Nope, didn't work.
Nope, didn't work. I tried exactly as you instructed and when I attempted to
delete the calendar from the global I got the same message as before, "You
cannot change an enterprise base calendar from here. Check out the
enterprise global to rename, edit, or delete enterprise base calendars."
Thanks and please don't give up yet.
~Peg Cornett
:
Re: Calendar won't
Peggy:
Are you certain that the calendar is not used in an project?
After deleting the calendar, are you exiting out of Project and restarting?
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:
http://www.msprojectexperts.com
For Project Server FAQS:
http://www.projectserverexperts.com
Dale and Gary ~I work in the same office as Peg, and she asked if I???d help
Dale and Gary ~
I work in the same office as Peg, and she asked if I???d help her with this
problem. After looking into it, I decided to restore the Enterprise Global
from our production system, and discovered a reproduction the pollution Peg
described.
We have maintained two calendars in both our production server Enterprise
Global and training server Enterprise Global ??? Standard and SENSOR. Prior to
my restore, I saw two calendars in the training Enterprise Global ??? Standard
and SENSOR1. After restoring, I could see three calendars ??? Standard,
SENSOR1, and SENSOR2 ??? the restore process apparently renamed the incoming
SENSOR calendar to SENSOR2. I had deleted all the projects off of the
server, but I was working with a template. In the template I could now see
four calendars ??? Standard, SENSOR, SENSOR1, and SENSOR2 ??? SENSOR was set as
the project calendar.
I tried several things, to include deleting the SENSOR1 and 2 calendars from
the Enterprise Global. I tried copying the SENSOR calendar from the template
to the Enterprise Global, setting the Enterprise Global to use the SENSOR
calendar, and then deleted SENSOR1 and 2. However, I could not delete
SENSOR1 and 2 from the Enterprise Global. It would appear they were deleted
in organizer, but saving, exiting MS Project, and re-launching proved that
they were still there.
I was finally able to eliminate all of the pollution by setting all the
templates and the Enterprise Global to the standard calendar, and deleting
all references to the SENSOR calendar. After considerable experimentation, I
have concluded that the only way I could get a clean restore of the
production Enterprise Global onto the training server was by eliminating
every reference to the SENSOR calendar on the training server to include the
Resource Pool. So I deleted SENSOR from all the templates and set the
project calendar to Standard. I also made sure there were no references to
either SENSOR1 or SENSOR2. After doing all this, the production Enterprise
Global restored cleanly to the training server.
After getting a clean restore, I backed it up, and restored it again. It
worked fine ??? no problem restoring an Enterprise Global backed up from the
same server. This showed me there is a problem with restoring an Enterprise
Global to a different server with the same custom base calendar name.
Indications in books, and conversations with our implementation vendor,
provided us confidence that we could safely restore our production Enterprise
Global to the training server. But this practice has resulted in polluting
our training server Enterprise Global. Further, it has exposed a bug that
precludes deleting an automatically renamed calendar in the context of this
scenario. I have proven to my satisfaction that if a calendar gets renamed
as I have described, it is in fact referenced somewhere on the server, so
cleaning up a server with hundreds of projects would be a real problem.
This is a little unnerving because recommendations I???ve read suggest making
updates to the Enterprise Global on a development server, testing it, and
then restoring it to the production server. However, my experience has made
me cautious. If I ever do that, I think I will delete the custom base
calendar from the development Enterprise Global prior to backup and restore
to the production system, and then copy to that Enterprise Global the desired
base calendar from a project or tempate on that server. I haven't had an
opportunity to try it yet, but that's what I think I'd try first.
--
Bob Zapf
:
Bob --I want to thank you for your careful examination of the problem and its
Bob --
I want to thank you for your careful examination of the problem and its
ultimate solution. I myself have always been wary about backing up the
Enterprise Global in one Project Server 2003 instance and then restoring it
in another. It has worked for some people, so I guess we should only do so
with extreme caution. Thanks so much for sharing the results of your fix
with us all. Let us all learn from your PAIN!
Re: Calendar won't
Bob:
My recommendation is not to restore Enterprise Global files between
instances. If you want to duplicate anything from production to training,
duplicate all of it by database restore. If you want to play with Enterprise
Global restores on different sites, then create a blank sandbox instance for
this purpose and use a database restore to refresh the sandbox between play
sessions.
--
Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:
http://www.msprojectexperts.com
For Project Server FAQS:
http://www.projectserverexperts.com
I have run into this same problem - we are following a standard code promotion
I have run into this same problem - we are following a standard code
promotion practice with global templates in a Project Server 2003
installation. We make changes to the global template in development, save
it, test it, then back it up and restore it to the production environment.
Every time we do this, each custom base calendar gets a '1' added to the end
- and then it deletes the original.
For example, we have 'CustomBase' in both environments. We change something
else (say, an Enterprise Outline Code value) in development and save it. We
backup the global template, then restore it to production. After exiting and
restarting Project Pro, we see 'CustomBase1' in production - and we can't
rename it or delete it.
We are using the custom calendars as task calendars.
Does anyone know if Project Server 2007 also has this bug? Calendars is the
only Organizer object this is happenning with.
Thanks,
Brian Lucas
:
Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Circular Progress Indicator
http://www.eggheadcafe.com/tutorial...a-cc047643fd42/wpf-circular-progress-ind.aspx