Paul

Update: The database server has finished loading all the databases and the service is now restored. -Paul

We do have a DR plan, the problem with it is that the DNS TTL is set to 24 hours. We're still evaluating our options. -Paul Update: The storage gateway is now online and our database cluster is starting up. -Paul

Nobody likes such situations but everyone's frustration is warranted. We keep asking our hosting provider for an ETA but we haven't received any so far. Our DR committee is evaluating the time it would take to restore the service in a failover DC. -Paul

Some more context for this situation: The hosting provider has rebuilt their storage gateway and they are having stability issues with it. Right now they are working on restoring it. -Paul

Locking this thread, please use this thread instead as it has more context: -Paul

We're in contact with the hosting provider, the initial estimate is that it should be less than half an hour left. Sorry for the inconvenience caused, it seems that something didn't go as planned with their maintenance. -Paul Please reach out to your account manager for all billing questions. -Paul

Hi there, Apologies for this. Our hosting provider is running overtime on their scheduled maintenance. I'll post another update when the service is back up. -Paul

The service is now restored. We apologize for the inconvenience caused. -Paul

Hi Dan, For the past hour we've been working on resolving a storage issue with our hosting provider, please check out this announcement post over here: We will post updates as we have them. We appreciate your understanding. -Paul

Hi Alec, Apologies for that. We've installed an update to the EAP server and that went wrong. Everything should go right now. -Paul

Hi Tyler, Thank you for the report. We've managed to identify the issue and we're working on a fix as we speak. -Paul

You should see the same screen in Pulseway for Bitdefender, can you attach a screenshot of what you see? -Paul

Hey @DJB, Try running the commands in this KB article and let me know if that did the trick: https://intercom.help/pulseway/en/articles/964192-error-1001-the-specified-service-already-exists -Paul

Hi Darien, Yes. That would be the cause of the database server finally starting up. Apologies for the inconvenience. Databases are still starting, will post another update when all services are completely back up. Update: 7:10PM: All services are now fully operational. -Paul

We're providing updates in this thread: -Paul

Yes Josh, apologies again. The root cause of the issue is impacted disk I/O where the SAN has experienced multiple disk failures at the same time greatly reducing I/O capacity. We'll announce tomorrow a maintenance window for the window where we will transition to a SSD-backed SAN which will greatly increase the performance of our cluster. Update: 5:14PM - We're down again. We've decided to switch to the new storage now. Update: 5:50PM - We're 20% done with the move to the new storage, we anticipate another 2 hours before we can restore service. Update: 6:24PM - 69% done with the move. Update: 6:58PM - Move completed successfully, databases are starting up. -Paul

Hey everyone, Apologies for the post-Halloween scare. We've worked with the hosting provider and have restored the service. We will be announcing later this week a maintenance window when we will be switching to a more modern storage solution. -Paul

The Pulseway Manager app will not show settings overridden by the endpoint policy but they settings do take effect in the monitoring service. Sorry for the confusion caused. -Paul

Excellent, glad to hear you've managed to get it installed. -Paul

It looks like the Pulseway agent isn't even installed. That's odd. Your best bet would be to copy the Pulseway folder from another computer and then manually register the service. Alternatively try using a tool such as CCleaner to remove the Pulseway app registration from the registry. -Paul

Hi there, Try running the following command as an administrator and then restart the Pulseway Manager app: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe "C:\Program Files\Pulseway\PCMonitorSrv.exe" -Paul

Hi there, You'd keep the double quotes in the script. -Paul

Hi there, If you have configured the Autotask integration from the Integrations page in the WebApp, you do not need to configure it again within endpoint policies. You get to pick which RMM Organizations, Sites and Agent Groups will forward notifications into tickets from the integration page. -Paul

Hey @TimStark, Please PM me the details and I'll work with you on getting it done. We do not provide any way of removing archived notifications within the product but we can organize an once-off exception for you to permanently delete the data but we'll need to go through a couple of steps, including identity verification. -Paul

Can you try to run it within a command prompt running as an administrator using this command? This will also generate an installation log file, please send us the log file in the event that the installation still errors out. Replace the Pulseway_x64.msi with the file name of the MSI. msiexec /i Pulseway_x64.msi /l*v install.log -Paul