have had this problem. Thought I need to reinstall and then took off previous versions. Finally, when I selected task by Row Number the inactivate button became active.
Do you still have the Backward Compatibility mode enabled on your project Server 2010.
Check under Server Settings >> Additional Server Settings
Inactivate feature is disabled when the BCM is enabled.
Be careful about disabling the BCM, though. You CANNOT re-enable it once you disable it.
Did you ever solve the Inactivate Task Problem? I recently migrated a large (3500 tasks) project from 2007 to 2010 Professional (2010 basic doesn’t have the “Inactivate” button or feature) and have had problems since. Now that I’ve migrated, I can’t get Task Activate / Deactivate to work. I followed the thread of your experience, but no one ever solved your fundamental problem. The inactivate task button always grayed out. 2010 is a buggy beast.
I created a dummy project and the function works fine – I can activate or deactivate tasks at will. But, my Project files that were created in 2007 do not respond. I find it frustrating that migrating a project over adversely affects the features.
Can anyone enlighten me? Thanks! Todd
The only time I run into this if I’ve opened a file previously saved in a compatible format. I actually just resave it as a Project file, don’t even have to close out, and the inactivate button is active. File, Save As, same name with format of Project; overwrite existing file.
Prasanna and AFridelle,
Thank you both for responding. I can’t imagine I’m the only one suffering from this, but I have not seen much traffic in the BLOGosphere.
1. Regarding Backward Capability: I have MSP2010 Professional, but am not using PWA features on server. Because the Inactivate Task (and Auto/Manual Schedule toggle) seems to work under some circumstances, I don’t think turning off the Backward Capability Mode should be necessary. Do you agree?
2. Regarding AFridelle’s comment: I agree that a legacy project file – say MSP2007 – should open in MSP2010 Professional and then I should be able to simply convert using SAVE AS an MSP2010 Project file. I’ve manually SAVED AS the files anyway, but that didn’t fix my problem.
3. I am open to suggestions. I fear I must copy the projects into a working template, which will be a lot of work and possibly introduce corruptions in my data. I have a MASTER and 12 SUBPROJECTS hammocked to that master with EXTERNAL links between the subprojects. I’ll need to validate all that data.
Keep the ideas coming! And thank you! Todd