cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X

DPM TIMELOSSTREND Not visible

Pratik_Aswale
12-Amethyst

DPM TIMELOSSTREND Not visible

Hello All,

 

I am working on DPM and have uploaded the default excel file which we get from github name is DPM sample 1.2.14. In Performance Anaysis page >> waterfall model >> timeloss trend i not loading

 

PFA 

1 ACCEPTED SOLUTION

Accepted Solutions
akharma
5-Regular Member
(To:Pratik_Aswale)

Could you attach the script log to this thread? There may be other messages that can lead to the cause. One possibility is that the collation of the database is incorrectly set. Can you check that the dpmdb is set to SQL_Latin1_General_CP1_CI_AS. Emphasis on the CI portion. That stands for Case Insensitive. If it is instead CS (case sensitive), certain database procedures will fail.

View solution in original post

5 REPLIES 5

Have you checked the log files?

Error in: PTC.PerformanceAnalysis.Manager.GetTimeLossDisplayData javascript service. Message ::This operation failed to execute. Please contact your administrator. (GetTimeLossDisplayData#106)
 
Getting this in script log

I think you will have either to look into the service code yourself or create a ticket with support. There are too many factors which could cause this to give advice here (at least for me).

If you get this fixed, please post the resolution here.

akharma
5-Regular Member
(To:Pratik_Aswale)

Could you attach the script log to this thread? There may be other messages that can lead to the cause. One possibility is that the collation of the database is incorrectly set. Can you check that the dpmdb is set to SQL_Latin1_General_CP1_CI_AS. Emphasis on the CI portion. That stands for Case Insensitive. If it is instead CS (case sensitive), certain database procedures will fail.

Hello,

Yes the collation wsa wrongly set that's wy I was facing the issue. The collation should be SQL_Latin1_General_CP1_CI_AS as discussed above.

 

 

Kudos

Atharva

Top Tags