Question

NETRONIC XGantt - The calendar "TEMPCAL#" is used, it can not be deleted


Userlevel 5
Badge +9
  • Sidekick (Customer)
  • 87 replies

We have just updated from Apps 10 Update 9 to Update 15, and now get the following error when searching in the Resource Monitoring Gantt.

You can search okay the first time, however if you then perform a subsequent search and change the search criteria, this error appears. It happens for that user until they close out of, and restart IFS.

It does not appear to happen when logged in as IFSAPP though.

It was not a problem prior to Update 15.

Ifs.Fnd.FndSystemException: Explorer: An Unhandled Exception has occurred ---> NETRONIC.XGantt.VcElementCannotBeDeletedException: The calendar "TEMPCAL#" is used, it can not be deleted.
at NETRONIC.XGantt.VcGantt.throwException(Type type, String message)
at ActXBaseControl.throwException(Type type, CStringT<wchar_t\,StrTraitMFC_DLL<wchar_t\,ATL::ChTraitsCRT<wchar_t> > >* message)
at NETRONIC.XGantt.NeAutoElementBaseCollection.removeElement(Char* elementName)
at NETRONIC.XGantt.VcCalendarCollection.Remove(String calendarName)
at Ifs.Application.Wo.frmMonitoringGantt.DrawCalendars()
at Ifs.Application.Wo.frmMonitoringGantt.loadEmployeeData()
at Ifs.Application.Wo.frmMonitoringGantt.frmMonitoringGantt_OnPM_DataSourcePopulate(Object sender, WindowActionsEventArgs e)
at Ifs.Application.Wo.frmMonitoringGantt.frmMonitoringGantt_WindowActions(Object sender, WindowActionsEventArgs e)
at PPJ.Runtime.Windows.SalWindow.InvokeWindowActions(WindowActionsEventArgs args, SalContext context, Int32 startIndex)
at PPJ.Runtime.Windows.SalWindow.FireWindowActions(Int32 msgCode, IntPtr wParam, IntPtr lParam)
at PPJ.Runtime.Windows.SalWindow.DispatchThenProcess(Message& m)
at PPJ.Runtime.Windows.SalWindow.ProcessWndProc(Message& m)
at PPJ.Runtime.Windows.SalForm.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
--- End of inner exception stack trace ---

 


13 replies

Userlevel 2
Badge +5

Hi!

Is there still trouble with the Monitoring Gantt?

If so.

After update, have you re-generated the calendars connected to resources groups and maintenance organizations? (Re-generation is needed after upgrade)

Is the “TEMPCAL#” a calendar that you have created and connected to a resource group or maintenance organization, or… in your environment? If yes, then is a re-generation fixing the issue? I’m asking because we don’t know the source to the error and are not sure if error is generated via error in IFS Applications basic data or if the error is generated due to an issue in our third part tool, Netronic.

Regards,

//Janne

Userlevel 5
Badge +10

@Garak 

How did you resolve this issue?  We have something similar.

Thanks.

Userlevel 5
Badge +9

Hi @jporter, no its still an ongoing problem unfortunately.

Userlevel 5
Badge +9

Hi @janise no, TEMPCAL#” is not used by us to our knowledge. It looks to me to be an internal/behind the scenes calendar in the application? These are the calendars we have.

 

Badge +1

Hi,   “TEMPCAL#” add to define empty calendars, (If there are resources which do not have any calendar information still Nettronic needs a calendar to draw that resource line ), We have done a correction in this area exactly for this type of issue. we will check it and update you. 

Cheers,

Mithila 

Userlevel 2
Badge +5

Part 1:

Hi!

Based on Mithila’s answer you get above I continued an internal investigation and find out that I could re-create the error in our environment. Please report to us and we can try to get it corrected from our third part supplier or if we can make an own correction…

Userlevel 2
Badge +5

Part2:

Anyway, secure that you have valid calendars connected to both the Maintenance Organization and the actual Resources in the resource Navigator if not HR are used. Calculate also the Resource Capacity in Resource Management/Resource Navigator and all works fine for you without any error.

Userlevel 2
Badge +5

Part3:

 

Userlevel 2
Badge +5

Part4:

If you are using HR Schedules to get Personal Resource availability, then you need to secure that all the actual resources are connected to valid schedules inside HR.

PS: Do not forget the Tools & facilities if such exist and should be display in the Gantt.

Regards,

//Janne

Userlevel 2
Badge +5

Hi @Garak and @jporter 

Please see the answer that I and Mithila has added to the  "TEMPCAL#" issue!

 

Have a Nice Day!

Regards,

//Janne

Userlevel 2
Badge +5

Hi @Garak,

Did you ever get this problem solved completely and could you explain what the fix was?

I can't follow what the responses above have tried to explain.

This is also a time-consuming nuisance problem for us.

 

Thanks

Cory

Userlevel 2
Badge +5

Hi @Cory 

Ensure that all resources are linked to a valid work time calendar in general Resource or a valid attendance schedule in Human Resources. The alternative is to install the fix with bug id: "165325".

The connection to a valid work time calendar is made on the resource in the "Resource/Resource Navigator" while the connection to a valid HR attendance schedule is done in HR. Regardless of which connection you use, you must run "Calculate Resource Capacity" in the Resource Navigator after the connection is made.

The easiest way to see which resources lack a valid calendar or schedule link is to see which lack presence in the Gantt. Ie: those that have completely gray rows without presence slots… for example ABB-TECH12 in the example below. 

Best Regards //Janne

Userlevel 2
Badge +5

Thanks @janise much appreciated

Reply