Can't open Project - Unexpected error occured during command execu
Michael M
Recently we have had trouble opening a project on Project server 2007 via
the Project client or Project server interface. The error we get is:
"An Unexpected error occured during command execution
Try the following:
Verify that all arguments names and vaules are correct and are of the
correct type.
You may have run out of memory. To free up avaliable memory, close programs,
Porjects, or windows that you aren't using. "
I have tried to open the working copy of the project in read only and
read\write mode with no luck. I have also tried to open the published version
of the project and had no luck.
Any ideas would be greatly appreciated.
Thanks
Michael
Dale Howard [MVP] dot at dot
Based on your description of the problem, I would strongly suspect that this
project has gotten corrupted somehow. If this is truly the case, then you
have two options:
1. Ask your Project Server administrator to perform an Administrative
Restore of this project using Server Settings > Administrative Restore in
PWA. Assuming he/she has the system set to atuomatically backup projects on
a daily basis, you could at least recover the project from yesterday, or
even a previous day, assuming he/she has set up the system to retain
multiple backups.
2. An alternate method, which works sometimes on corrupted projects is to
insert the project in a new blank project. To do this, launch Project
Professional 2007 and connect to Project Server. In a blank project, click
Insert - Project. Select the problem project and click the Insert button.
Beyond the above, I'm not aware of any other way to address the problem of
not being able to open the project. Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
"Michael M" <Mich...@discussions.microsoft.com> wrote in message
news:A5AD7793-B1FE-4AED...@microsoft.com...
Michael M
Thanks for your quick response.
I suspected the project was corrupt, but was hoping there was a quick fix.
If we haven't perform automative backups, could we
1.Do a restore of the DB's, say before the problem occured in a test
environment
2.Export the data out into a project file - MPP
3.Delete the project in Live
4.Recreate\import the project using the saved file
If this is possible, do you think this would create any data inconsistency
in Project server?
If not, then all that would be lost, is any time entered after the restored
time.
Thanks again.
Dale Howard [MVP] dot at dot
Yes, your approach should certainly work. In Project Server 2003, the only
way to restore a project from a DB backup was using the method you describe.
I would recommend you try the second approach in my previous method first,
and then fall back to your suggested approach in your latest post only if
necessary. If the corrupted project has Risks, Issues, Documents, or
Deliverables in its Project Workspace, then refer to the following to
preserver the Project Workspace when deleting the corrupted project:
http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/DeleteProjectWithoutSubweb.aspx
Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
"Michael M" <Mich...@discussions.microsoft.com> wrote in message
news:7E95F06D-A1F0-4CF4...@microsoft.com...
Michael M
Just to give you an update, I had to fallback to the backup and restore
approach(I couldn't even insert the project). I then imported the MPP as per
documented. Everything worked fine. Then after 3 hours, the project got
corupt again. The only thing I could think of was a corrupt cache(since we
retained the exact project name). I then had the project manager create a new
project and copy and paste the project data into the new project. We then had
everyone who access the project to clear their local cache and then imported
the project back in.
I then perform an Administrative backup so we could easily restore if it
occured again
Question
1. Any reason why the project would corrupt again
2. Does Microsoft provide any utility to check files for corruption, or is
there any easy checks to do?
Thanks for your assistance.
Dale Howard [MVP] dot at dot
1. I am not aware of any way to pinpoint why a project became corrupted.
On the other hand, one of the leading causes for project corruption is
cutting and pasting, or copying and pasting, tasks within the project or
tasks from another project. This process creates duplicate unique ID
numbers, which is a bad thing. Is there any possibility that the PM of the
corrupted project has been doing copying/cutting/pasting tasks in this
project or from another project?
2. To the best of my knowledge, no, Microsoft has not released a tool to
determine whether a project is corrupted. Usually the way to tell is
looking for weird behavior in a project, such as that the project will not
publish, no matter how many times the user tries, or that you cannot open
the project any more.
Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
"Michael M" <Mich...@discussions.microsoft.com> wrote in message
news:43051D38-AD27-454E...@microsoft.com...
David Hunsberger
circumstances when this occurs. In my experience it began happening only
after I applied Project 2007 SP2, and it only happened when I had the save
option (Tools-Options-Save) set to always save as Project 2000-2003. My
workaround is to save the file routinely as 2007 (change Tools-Options-Save
to 2007), and then only do a final "save as" 2003 when I need to send out to
teammates who require the older format. Since I changed my save option to
2007 I have had no recurrence of this problem, but prior to that it would pop
up after the second or third time saving any file, even small files, and it
would keep popping up every time thereafter. Very annoying. I am guessing
something in 2007 SP2 created this error.
- David Hunsberger, former MCP in Project (1995)
MS Project instructor and consultant. www.it7.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dale Howard [MVP] dot at dot
Your comments are sage. Thanks for sharing! :)
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
"David Hunsberger" <DavidHu...@discussions.microsoft.com> wrote in
message news:F1F38F0F-409D-4ABB...@microsoft.com...
ProjectAnalyst
describe.
The problem was our SQL Server was using over 50% of available memory to
apparently do nothing. We're not sure why this occurred yet, but when we
switched over to the backup SQL Server in the cluster, managers were
immediately able to open their projects again.
For systems not using a cluster, i would recomend restarting the SQL Server
Service, or rebooting the SQL Server.
Pablo
http://weblogs.asp.net/pabloperalta/archive/2010/05/27/can-t-open-project-unexpected-error-occurred-during-command-execution.aspx
Dale Howard [MVP] wrote:
Michael M --Based on your description of the problem, I would strongly suspect
31-Aug-09
Michael M --
Based on your description of the problem, I would strongly suspect that this
project has gotten corrupted somehow. If this is truly the case, then you
have two options:
1. Ask your Project Server administrator to perform an Administrative
Restore of this project using Server Settings > Administrative Restore in
PWA. Assuming he/she has the system set to atuomatically backup projects on
a daily basis, you could at least recover the project from yesterday, or
even a previous day, assuming he/she has set up the system to retain
multiple backups.
2. An alternate method, which works sometimes on corrupted projects is to
insert the project in a new blank project. To do this, launch Project
Professional 2007 and connect to Project Server. In a blank project, click
Insert - Project. Select the problem project and click the Insert button.
Beyond the above, I am not aware of any other way to address the problem of
not being able to open the project. Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
Previous Posts In This Thread:
On Monday, August 31, 2009 7:39 AM
Michael M wrote:
Can't open Project - Unexpected error occured during command execu
Hi All,
Recently we have had trouble opening a project on Project server 2007 via
the Project client or Project server interface. The error we get is:
"An Unexpected error occured during command execution
Try the following:
Verify that all arguments names and vaules are correct and are of the
correct type.
You may have run out of memory. To free up avaliable memory, close programs,
Porjects, or windows that you are not using. "
I have tried to open the working copy of the project in read only and
read\write mode with no luck. I have also tried to open the published version
of the project and had no luck.
Any ideas would be greatly appreciated.
Thanks
Michael
On Monday, August 31, 2009 8:53 AM
Dale Howard [MVP] wrote:
Michael M --Based on your description of the problem, I would strongly suspect
Michael M --
Based on your description of the problem, I would strongly suspect that this
project has gotten corrupted somehow. If this is truly the case, then you
have two options:
1. Ask your Project Server administrator to perform an Administrative
Restore of this project using Server Settings > Administrative Restore in
PWA. Assuming he/she has the system set to atuomatically backup projects on
a daily basis, you could at least recover the project from yesterday, or
even a previous day, assuming he/she has set up the system to retain
multiple backups.
2. An alternate method, which works sometimes on corrupted projects is to
insert the project in a new blank project. To do this, launch Project
Professional 2007 and connect to Project Server. In a blank project, click
Insert - Project. Select the problem project and click the Insert button.
Beyond the above, I am not aware of any other way to address the problem of
not being able to open the project. Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
On Monday, August 31, 2009 10:51 AM
Michael M wrote:
Hi Dale,Thanks for your quick response.
Hi Dale,
Thanks for your quick response.
I suspected the project was corrupt, but was hoping there was a quick fix.
If we have not perform automative backups, could we
1.Do a restore of the DB's, say before the problem occured in a test
environment
2.Export the data out into a project file - MPP
3.Delete the project in Live
4.Recreate\import the project using the saved file
If this is possible, do you think this would create any data inconsistency
in Project server?
If not, then all that would be lost, is any time entered after the restored
time.
Thanks again.
"Dale Howard [MVP]" wrote:
On Monday, August 31, 2009 11:02 AM
Dale Howard [MVP] wrote:
Michael M --Yes, your approach should certainly work.
Michael M --
Yes, your approach should certainly work. In Project Server 2003, the only
way to restore a project from a DB backup was using the method you describe.
I would recommend you try the second approach in my previous method first,
and then fall back to your suggested approach in your latest post only if
necessary. If the corrupted project has Risks, Issues, Documents, or
Deliverables in its Project Workspace, then refer to the following to
preserver the Project Workspace when deleting the corrupted project:
http://www.projectserverexperts.com/ProjectServerFAQKnowledgeBase/DeleteProjectWithoutSubweb.aspx
Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
On Friday, September 04, 2009 11:21 PM
Michael M wrote:
Hi Dale,Just to give you an update, I had to fallback to the backup and
Hi Dale,
Just to give you an update, I had to fallback to the backup and restore
approach(I could not even insert the project). I then imported the MPP as per
documented. Everything worked fine. Then after 3 hours, the project got
corupt again. The only thing I could think of was a corrupt cache(since we
retained the exact project name). I then had the project manager create a new
project and copy and paste the project data into the new project. We then had
everyone who access the project to clear their local cache and then imported
the project back in.
I then perform an Administrative backup so we could easily restore if it
occured again
Question
1. Any reason why the project would corrupt again
2. Does Microsoft provide any utility to check files for corruption, or is
there any easy checks to do?
Thanks for your assistance.
"Dale Howard [MVP]" wrote:
On Saturday, September 05, 2009 2:02 PM
Dale Howard [MVP] wrote:
Michael M --1.
Michael M --
1. I am not aware of any way to pinpoint why a project became corrupted.
On the other hand, one of the leading causes for project corruption is
cutting and pasting, or copying and pasting, tasks within the project or
tasks from another project. This process creates duplicate unique ID
numbers, which is a bad thing. Is there any possibility that the PM of the
corrupted project has been doing copying/cutting/pasting tasks in this
project or from another project?
2. To the best of my knowledge, no, Microsoft has not released a tool to
determine whether a project is corrupted. Usually the way to tell is
looking for weird behavior in a project, such as that the project will not
publish, no matter how many times the user tries, or that you cannot open
the project any more.
Hope this helps.
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
On Monday, September 14, 2009 1:26 PM
David Hunsberger wrote:
Dale, I've been experiencing this problem and have narrowed down the
Dale, I have been experiencing this problem and have narrowed down the
circumstances when this occurs. In my experience it began happening only
after I applied Project 2007 SP2, and it only happened when I had the save
option (Tools-Options-Save) set to always save as Project 2000-2003. My
workaround is to save the file routinely as 2007 (change Tools-Options-Save
to 2007), and then only do a final "save as" 2003 when I need to send out to
teammates who require the older format. Since I changed my save option to
2007 I have had no recurrence of this problem, but prior to that it would pop
up after the second or third time saving any file, even small files, and it
would keep popping up every time thereafter. Very annoying. I am guessing
something in 2007 SP2 created this error.
- David Hunsberger, former MCP in Project (1995)
MS Project instructor and consultant. www.it7.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Dale Howard [MVP]" wrote:
On Tuesday, September 15, 2009 10:39 PM
Dale Howard [MVP] wrote:
David --Your comments are sage. Thanks for sharing!
David --
Your comments are sage. Thanks for sharing! :)
--
Dale A. Howard [MVP]
VP of Educational Services
msProjectExperts
http://www.msprojectexperts.com
http://www.projectserverexperts.com
"We write the books on Project Server"
On Thursday, September 17, 2009 2:50 PM
ProjectAnalyst wrote:
Michael, today I experienced this same error message and behavior you describe.
Michael, today I experienced this same error message and behavior you
describe.
The problem was our SQL Server was using over 50% of available memory to
apparently do nothing. We're not sure why this occurred yet, but when we
switched over to the backup SQL Server in the cluster, managers were
immediately able to open their projects again.
For systems not using a cluster, i would recomend restarting the SQL Server
Service, or rebooting the SQL Server.
"Michael M" wrote:
Submitted via EggHeadCafe - Software Developer Portal of Choice
Distributed Data Grids - Share Objects Between Windows Service and ASP.NET
http://www.eggheadcafe.com/tutorials/aspnet/953ed61f-e440-4ca5-8b7a-1bb00e33db07/distributed-data-grids-.aspx
Gary L. Chefetz
This probably could be rectified by using a different installation
procedure.
Uninstall Project 2007 and 2010
Install Project 2010
Install Project 2007
Run a repair on Project 2010 (fixes what the 2007 install breaks)
See if this still happens
Next time post the information in your question rather than sending everyone
to a blog.
--
Gary L. Chefetz, MVP, MCT, MCTIP
Business: http://www.msprojectexperts.com
FAQs: http://www.projectserverexperts.com
BLOG: http://www.projectserverhelp.com
"Pablo" wrote in message news:20105271542...@gmail.com...