@blackdraft, assuming you're referring to the error @integritydan mentioned, my advice to you is to ensure that you've fully attempted to tie up any loose ends on your side --- can prove it
Here's a hypothetical scenario --- based on stuff I often unwittingly witness at work --- to show how this can matter...
- An employee contacts a helpdesk technician, complaining that he can't login to the CRM app at this desk.
- The helpdesk technician rules out the usual stuff (n/w connectivity, redundant cache, etc.) & then escalates this to the app administrator.
- The app administrator ensures that his app's working fine, & contacts the virtualization administrator.
- The virtualization administrator detects a communication issue, & contacts the network engineer.
- The network engineer checks & assures him that nothing's been done by him / his team, & then contacts the security administrator --- who also has access to his switches / firewalls.
- The security administrator admits that he made some changes on the firewall as part of a security measure, & agrees that it's impacted the CRM app. He rectifies those changes, & shortly, all's OK...
Or so it seems...
The employee couldn't accomplish some tasks in time --- & this has consequences. Management doesn't accept that he couldn't use the CRM system, & alas, he can't prove that he'd duly contacted the necessary parties. (They in turn claim that all was OK on their side, & they weren't communicated with properly)
Bottom line: Even if the system is at fault, it's the user who often pays the price...
To reduce the risk of becoming that user, ensure that this isn't related to your systems, accounts, connection, time, etc. Also take screenshots / transcripts / printouts of whatever you can --- including your communication with support.
Last but not least, make sure that you've painted your picture properly, & have support confirm that they see it just well as you can...
Shannon D'Cruz,
CISM, CISSP
www.linkedin.com/in/shannondcruz
