Mark McElhenny

We are running iTop 2.7.7 and we have two mailboxes bringing tickets into iTop. We currently have one trigger (Object Creation) that sends out an email to both the end user and the IT team. However I've been asked if its possible to split it out. So that when emails come in from one mailbox an email gets sent to one part of the IT Team (Applications) and the end user with its own message and when they come in from the other mailbox a message gets sent to the IT Tech team and the end user again with...

We currently have 297 errors in our Synchro pull from AD into iTop. All of which have the same error: Unable to update the destination object: Object not following integrity rules: issues = Unexpected value for attribute 'status': Value not allowed [obsolete], class = Person, id = 717 Now for Status we have 2 options Active and Inactive when an account in AD is disabled it populates the .csv file with Inactive. When I look at the record on iTop it has the Status set to inactive so I'm not sure what...

I've attached the cron job php file

Ok update, if I run the above cron job from my old 2.4.1 itop folder it works, so something within the iTop 2.7.7 version has changed

Morning, In order to use OAUTH2.0 we have upgrade out iTop server both the iTop to 2.7.7 and also the OS Ubuntu from 16.04 to 20.04 (PHP7.0 to PHP7.4) Everything is working fine including the OAUTH part except for 2 Cron Jobs. The first is the one that sends out a daily report of contracts that are nearing the end. When I run the cron job manually it fails with the below error: PHP Fatal error: Uncaught Error: Cannot instantiate abstract class AbstractWeeklyScheduledProcess in /var/www/html/itop2.7.7/cron/cronprovidercontract.php:234...

Morning, In order to use OAUTH2.0 we have upgrade out iTop server both the iTop to 2.7.7 and also the OS Ubuntu from 16.04 to 20.04 (PHP7.0 to PHP7.4) Everything is working fine including the OAUTH part except for 2 Cron Jobs. The first is the one that sends out a daily report of contracts that are nearing the end. When I run the cron job manually it fails with the below error: PHP Fatal error: Uncaught Error: Cannot instantiate abstract class AbstractWeeklyScheduledProcess in /var/www/html/itop2.7.7/cron/cronprovidercontract.php:234...

Giorgio thank you. Your 2nd post is what our issue was, we were logged in as our own accounts as the mailbox account does not have access to azure. Logged out of office.com and logged back in with the mailbox credentials went back to iTop and regenerated a new token and everything is now working fine. I'll make sure to note that for future! Thanks again as it was a concern with two weeks until MS pull the plug!

We have upgraded our production system to 2.7.7 and everything is working fine including our standard email to ticket inbox. I have created the OAUTH2 in both itop and Azure and generated the token. I've the created the the OAUTH2.0 mailbox (Same inbox that's setup for the standard inbox) and when I go the mailbox content it says: Failed to initialize the mailbox: ?????@???.com. Reason: cannot change folder, maybe it does not exist Initially I left the mail box (For IMAP) blank like my standard mailbox,...