![]() |
| |||||||
![]() |
| | LinkBack | Thread Tools | Search this Thread | Display Modes |
| ||||
| Quote:
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
| Sponsored links |
| |
| ||||
| Quote:
I'm not aware of a way to back up the information it changes... best I can offer is to practice on a dev machine... but that will likely do little to mitigate the risk on the production system. Backing up the DB is a good idea, but I think most of the information that EditSite changes is in the registry. You may want to take a backup of that as well. You can find more information on the EditSite tool in the PS03 Installation Guide
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
| |||
| Quote:
![]() |
| |||
| Hi ssanderlin, I've installed the EditSite Tool on my Project Server 2003 and did the things following to the instructions below: Reset the DSN. 1. If you are running Project Server 2003, start the EditSite tool. If you are running Project Server 2002, start the Site Editor tool. 2. In the DSN Name box under Site Information, rename the existing DSN by adding a number to the end of the name. For example, if you are running Project Server 2002 and the name of the DSN is PC10DSN, rename the DSN to PC10DSN1. 3. Click Save, and then click Yes when you are prompted to delete the old DSN. 4. When you receive the message that the changes that you made are saved, click OK. 5. In the DSN Name box under Site Information, change the name of the DSN to the original name. To do this, remove the number that you added to the end of the name so that the DSN uses the original name of the DSN. For example, if you renamed the DSN to PC10DSN1 in step 2, change the name to PC10DSN. 6. Click Save, and then click Yes when you are prompted to delete the old DSN. 7. When you receive the message that the changes that you made are saved, click OK. 8. To verify that connection parameters are configured correctly, click Test under Virtual Directory, 9. Click OK, and then click Exit. But it's not work!!!! After reset DSN, I clicked "Update Now" to force the cube to build. 7 errors and 2 warnings are still shown on Application Event Logs. What should I do next ??? ![]() Jee Last edited by jeejangs; 04-24-2008 at 06:15 AM. |
| |||
| Problem Solved!!!! Problem caused : One resource name from my 2,400 resources has problem in its properties. Solution : 1. Open Microsoft Project Pro --> Tools --> Enterprise Options --> Open Enterprise Resources Pool 2. Select all resource name and Open . 3. If some resource name has problem, you will see the windows popup with memory error messages. ( This error 's really not described a real reason of problem.) I could not open all resource name at the same time. 4. I tried to check out resource name by splited them into small group until I found 1 user which cause this problem (from 2400 resource name). 5. Open SQL Analyzer and delete properties of this resource name. delete from MSP_TEXT_FIELDS where proj_id=1 and TEXT_REF_UID=2764 **"proj_id=1" means Enterprise Resource Pool; "TEXT_REF_UID=2764" means this problem resource "RES_UID=2764". Before deleted,please backup this table firstly. 6.After deleted , I re-enter the properties for this resource again and Rebuild the cube by pressing "Update Now" button from PWA. 7. CUBE WAS SUCCESSFULLY BUILT. IT'S BEEN DONE!!! PS.Thank you for David who gave me this solution. ![]() Wish this could help. Last edited by jeejangs; 05-12-2008 at 08:44 AM. |
| ||||
| Ack -- I missed your reply to me. Sorry! ![]() I'm glad you found a resolution!
__________________ Stephen Sanderlin Founder/Owner - EPMFAQ Principal Consultant - MSProjectExperts If you found this message useful, please click the Thanks button in the post! This electronic message, along with any information, advice, and opinions it contains, are mine alone and are not representative of my employer. All information is provided in "GOOD FAITH" and on an "AS IS" basis only. I provide no presentations or warranties, express or implied, including implied warranties of fitness for a particular purpose, merchantability, title, and noninfringement. I strongly advise you to extensively test any changes, workarounds, or techniques described herein on a development system prior to implementation in a production environment, and you are hereby notified that I bear no responsibility whatsoever for any loss, harm, or otherwise negative outcomes resulting from your actions, whether or not said actions were a result of this electronic message, directly or indirectly. |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|