Showing posts with label Clarity With Issues and Resolution. Show all posts
Showing posts with label Clarity With Issues and Resolution. Show all posts

Thursday, March 21, 2013

MSP Is not opening

you can find the default attribute by using this table cmn_attributes table in the database.



  In future, if you receive this kind of issue, please go and check in MSPField table and should not be available any custom fields which is not available in cmn_attributes table.
                This issue I replicated by adding one more row with dummy value which is not available in cmn_attributes. I received the same issue and shown to Karthik (Support team).
                

Thursday, March 14, 2013

Schedule link error in MSP – ShedLink MFC Application has stopped working.


Impact:
all users
Analysis
I have done nearly some 50 combination testing to find the root cause and have replicated the same issue today in the QA environment and found the root cause is custom field attribute which is “included in database table “mspfield” and not there as per guideline CA and may be some update happen unknowingly.
Root cause
There is a table called “mspfield” in database and found many custom fields are stored.

Work Around
Deleted all the custom fields in MSPField table, the attribute which is not available in cmn_attributes table.

Permanent solution
I am in the process of finding system or someone. who was added the custom fields in “mspfield” field.
           

Wednesday, March 13, 2013

Microsoft Project Issue with Clarity

We faced the below in our company and found that custom fields we need to delete in this table

MSPField table in database.

Impact:
All the users will face this issue.
Analysis
I have done nearly some 50 combination testing to find the root cause and have replicated the same issue today in the QA environment and found the root cause is custom field attribute which is “included in database table “mspfield” and not there as per guideline CA and may be some update happen unknowingly.
Root cause
There is a table called “mspfield” in database and found many custom fields are stored.

Work Around
Deleted all the custom fields in MSPField table, the attribute which is not available in cmn_attributes table.

Permanent solution
I am in the process of finding system or someone. who was added the custom fields in “mspfield” field.