Prev: Highligt a Date in Project 2003?
Next: Printing Reports
From: Ansley on 20 May 2010 09:26 I recieved the same error on a test file...very small "JulieS" wrote: > Can you create a quick file now, set a password and see if you > can create the same error? > > > Julie > Project MVP > > Visit http://project.mvps.org/ for the FAQs and additional > information about Microsoft Project > > On 5/18/2010 9:13 AM, Ansley wrote: > > This is installed on a terminal server, so users are accessing from their > > profile. As far as I know it was created with all the updates. Fairly > > certian. > > > > "JulieS" wrote: > > > >> Hello Ansley, > >> > >> There were some early reports of errors working with password > >> protected files in Project 2007. You mention that you have all > >> updates installed to 2007. Was this a file created without all > >> service packs installed initially? > >> > >> I hope this helps. Let us know how you get along. > >> > >> Julie > >> Project MVP > >> > >> Visit http://project.mvps.org/ for the FAQs and additional > >> information about Microsoft Project > >> > >> On 5/17/2010 2:46 PM, Ansley wrote: > >>> I put a write password on my project file. When I open it I get prompted for > >>> read-only which I select. However, it gives me an error that the file has > >>> too many rows, suggest to delete some or put in subreports. My file has no > >>> database, only 37 rows, I'm using 2007 with all the updates. If i take off > >>> the write protection it opens fine. Help is appreciated. Thanks Ansley > >> . > >> > . >
From: JulieS on 20 May 2010 15:22
Hmmm. I've just run a quick test here -- Project Pro 2007 SP-2 not connected to server (neither Project Server nor terminal server) I get repeated "unexpected errors 0x8C04001B" when trying to save an existing file with a write reservation password. Unable to save a write reservation password. New file -- never saved before. No trouble this time saving with a write reservation password. Open file with "read-only" no errors. Close the file. Re-open and provide the password. No errors. Able to save and re=open without error. However, the initial error which I can reproduce on all files plus your comments lead me to say I would not use password on Project files. Sorry I didn't have a better answer. Julie Project MVP Visit http://project.mvps.org/ for the FAQs and additional information about Microsoft Project On 5/20/2010 9:26 AM, Ansley wrote: > I recieved the same error on a test file...very small > > "JulieS" wrote: > >> Can you create a quick file now, set a password and see if you >> can create the same error? >> >> >> Julie >> Project MVP >> >> Visit http://project.mvps.org/ for the FAQs and additional >> information about Microsoft Project >> >> On 5/18/2010 9:13 AM, Ansley wrote: >>> This is installed on a terminal server, so users are accessing from their >>> profile. As far as I know it was created with all the updates. Fairly >>> certian. >>> >>> "JulieS" wrote: >>> >>>> Hello Ansley, >>>> >>>> There were some early reports of errors working with password >>>> protected files in Project 2007. You mention that you have all >>>> updates installed to 2007. Was this a file created without all >>>> service packs installed initially? >>>> >>>> I hope this helps. Let us know how you get along. >>>> >>>> Julie >>>> Project MVP >>>> >>>> Visit http://project.mvps.org/ for the FAQs and additional >>>> information about Microsoft Project >>>> >>>> On 5/17/2010 2:46 PM, Ansley wrote: >>>>> I put a write password on my project file. When I open it I get prompted for >>>>> read-only which I select. However, it gives me an error that the file has >>>>> too many rows, suggest to delete some or put in subreports. My file has no >>>>> database, only 37 rows, I'm using 2007 with all the updates. If i take off >>>>> the write protection it opens fine. Help is appreciated. Thanks Ansley >>>> . >>>> >> . >> |