Goline Logo

FAQ

News

  • New Partnership Between Goline and EaseUS: Technology and Innovation at Your Service. We are excited to announce our collaboration with EaseUS, a leading company in data management, file recovery, and disk cloning software. This collaboration allows us to provide our users with reliable and cutting-edge tools to manage and protect their devices efficiently. Exploring the Benefits of Our New Partnership with EaseUS This collaboration enhances our capability to deliver top-notch services to our community. With EaseUS, you can optimize storage space, recover lost files, and clone disks easily and securely. Whether you're a home user or an IT professional, you'll...
  • GOLINE SA partner with FileCloud November 25th, 2024
  • In the supply and logistics sectors, email communication is pivotal. However, organizations face threats like email fraud and phishing. GOLINE SA's clients struggled with configuring email authentication protocols manually. To address this challenge, GOLINE SA partners with PowerDMARC as an MSP Partner, collaborating to streamline implementation and management. PowerDMARC's cloud-based platform automated DMARC, SPF, and DKIM protocols for GOLINE SA's clients. This streamlined the transition to DMARC enforcement policies, bolstering domain protection without compromising email deliverability. The intuitive platform facilitated easy navigation and provided detailed reporting for proactive issue resolution. Strategic Collaboration: GOLINE SA Partners with PowerDMARC GOLINE SA's clients...

MS Exchange DAG Maintenance error (exiting from script)

Exchange DAG Maintenance – cluster.exe issue (5058)

 

Today, on a DAG maintenance of an Exchange 2016, I ran into the problem that after executing the script StopDagServerMaintenance.ps1 a warning was displayed.

 

Call-ClusterExe: cluster.exe did not succeed, but 5058 was not a retry-able error code. Not attempting any other servers. This may be an expected error by the caller.

 

 
 
 

 

After a little troubleshooting I found that after running the scripts StartDag ServerMaintenance.ps1, the cluster node has not been paused and in the StopDagMaintenance.ps1 script, this will be checked and reseted so the cluster node is up again – what causes an error.

 

 
 
 

 

I will show you the problem and how I (and you too) could fix it.

 

Note: You need to always run the Exchange Management Shell as administrator.

 

 

After I got the problem, I looked at the script more closely and found that Microsoft has set a $false for the pauseClusterNode instead of a $true.

 

 
 
 

 

I have changed this to $true and saved the script.

 

Note: To do this, run the PowerShell ISE as administrator and open the script.

 

 
 
 

 

I then executed the script again and checked the state using Get-ClusterNode and now the cluster node was paused.

 

 
 
 

 

Now, when I run the StopDagServerMaintenance.ps1 script, the error no longer occurred.

 

 
 
 

 

Enjoy and take care!

5 3 votes
Article Rating
Subscribe
Notify of
0 Comments
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x