Re: Strange error when publishing projects

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Gary L. Chefetz \(MVP\) ("Gary)
Date: 10/12/04 

Date: Tue, 12 Oct 2004 07:19:05 -0400

Novica:

The error indicates key duplication in the database. As I'm not able to look
over your shoulder, it's difficult to say what's going on or what exactly is
causing it. If the duplication already exists in the database, you need to
track it down and remove it. Typically you can do this by removing the
affected plan from the database by saving it as an mpp file, then deleting
it from Project Server and reimporting it using the import wizard. 

-- 
Gary L. Chefetz, MVP
"We wrote the book on Project Server
http://www.msprojectexperts.com
-
"Novica B" <Novica B@discussions.microsoft.com> wrote in message
news:00BCBCC3-3466-4832-9EFD-F47F66AB7427@microsoft.com...
> Gary,
> I took your advice about "copy and paste" and re-typed a schedule without
> copy/cut and paste, to test our system, unfortunately it didn't resolve
the
> problem, we are still getting the task error as before.
>
> Do you have any more suggestions? We are getting desperate.
>
> Thanks
>
> "Gary L. Chefetz (MVP)" wrote:
>
> > Your error is completely different. Sounds like you've cutting and
pasting
> > entire rows in your project plan. That's a big no-no in enterprise
plans.
> >
> > -- 
> >
> > Gary L. Chefetz, MVP
> > "We wrote the book on Project Server
> > http://www.msprojectexperts.com
> >
> > -
> > "Novica B" <Novica B@discussions.microsoft.com> wrote in message
> > news:90B57D31-DE30-4797-B48E-5CE67B1D8B74@microsoft.com...
> > > Gary,
> > > I am having the same problem as James, plus one more, I also get
> > > "[Microsoft][ODBC SQL Server Driver][SQL Server] Cannot insert
duplicate
> > key
> > > row in object
> > > 'MSP_TASKS' with unique index 'I_MSP_TASKS'."
> > >
> > > I have asked my system adminstrators to check error logs immediately
after
> > > the error occured and nothing is coming through to the server. We have
> > > installed the "Project Server 2003 SetTracing Utility" and it can't
see
> > > anything. I have tried reinstalling the software on the affected
machines
> > and
> > > there is no change.
> > >
> > > From what i can tell it is a Local Machine, but how is the problem
> > spreading
> > > to other machines?
> > >
> > > This is becoming a big problem.
> > >
> > > Can you help
> > >
> > > "Gary L. Chefetz (MVP)" wrote:
> > >
> > > > James:
> > > >
> > > > OK, you're certainly doing that correctly. What's the context of
this
> > error?
> > > > Is this a brand new install or suddenly happening on an existing
system?
> > > > What errors do you see in the server application event log?
> > > >
> > > > -- 
> > > >
> > > > Gary L. Chefetz, MVP
> > > > "We wrote the book on Project Server
> > > > http://www.msprojectexperts.com
> > > >
> > > > -
> > > > "James" <anonymous@dicussions.microsoft.com> wrote in message
> > > > news:#x#QW4raEHA.716@TK2MSFTNGP11.phx.gbl...
> > > > > Hi Gary,
> > > > >
> > > > > I go to New, then select an Enterprise template from the
Enterprise
> > > > > templates tab. One this has loaded I then save it as "XYZ Project"
to
> > the
> > > > > Project server DB (the default).
> > > > >
> > > > > After that I use Build team from enterprise to buld the resource
list
> > in
> > > > the
> > > > > project, then assign resources to tasks. After that I save the
project
> > > > again
> > > > > and then go to publish the  New and Changed Assignments.
> > > > >
> > > > > Its this last save that takes ages, although it does eventually
work.
> > > > >
> > > > > I don't know what you mean by a flwaed project creation path. I am
> > > > following
> > > > > all the steps as per the guidance in the Microsoft Project
> > documentation.
> > > > >
> > > > > I'd be grateful for any advice...
> > > > >
> > > > > Thanks
> > > > >
> > > > > James
> > > > >
> > > > > "Gary L. Chefetz (MVP)" <gary.nospam at chefetz.org> wrote in
message
> > > > > news:OrogTNmaEHA.3016@tk2msftngp13.phx.gbl...
> > > > > > James:
> > > > > >
> > > > > > It sounds as though you may be following a flawed project
creation
> > path.
> > > > > > Exactly how are you "loading and Enterprise Template?"
> > > > > >
> > > > > > -- 
> > > > > >
> > > > > > Gary L. Chefetz, MVP
> > > > > > "We wrote the book on Project Server
> > > > > > http://www.msprojectexperts.com
> > > > > >
> > > > > > -
> > > > > > "James" <anonymous@dicussions.microsoft.com> wrote in message
> > > > > > news:O0pHurdaEHA.1000@TK2MSFTNGP12.phx.gbl...
> > > > > > > Hi,
> > > > > > >
> > > > > > > We have encountered an issue when publishing projects.
> > > > > > >
> > > > > > > Here's what we are doing :-
> > > > > > >
> > > > > > > 1)  Load an Enterprise Template
> > > > > > > 2)  Save the project as a new name to the project server DB
> > > > > > > 3)  Use Build team from enterprise to assign resources to the
> > project
> > > > > > > 4)  Assign resources to project tasks
> > > > > > > 5)  Publish the project assignments
> > > > > > >
> > > > > > > But at this last step, it takes ages to save the project (10
> > minutes
> > > > or
> > > > > > > more) and there are no more tha 100 tasks in it.  Eventually
it
> > > > displays
> > > > > > an
> > > > > > > error dialog"[Microsoft][ODBC SQL Server Error]Communication
link
> > > > > failure"
> > > > > > >
> > > > > > > If I clik OK, nothing happens and it does appear to have saved
the
> > > > plan.
> > > > > > >
> > > > > > > Then, if I later try to perform updates on the plan from
submitted
> > > > > > time***
> > > > > > > entries, I get another error coming up "[Microsoft][ODBC SQL
Serve
> > r
> > > > > > > Driver][SQL Server] Cannot insert duplicate key row in object
> > > > > > > 'MSP_RESOURCES' with unique index 'I_MSP_RESOURCES'.
> > > > > > >
> > > > > > > I then can't save the project. No matter what I do the system
will
> > not
> > > > > > allow
> > > > > > > me to save the project.
> > > > > > >
> > > > > > > Can you tell me what this means and how we solve it please ?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > James
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Quantcast