Posts

Showing posts from April, 2019

Creating root certificate and client certificate to establish a VPN connection to cloud from On premises.

Creating root certificate and client certificate to establish a VPN connection to cloud from On premises. We can run the below commands from power shell $cert = New-SelfSignedCertificate -Type Custom -KeySpec Signature ` -Subject "CN=ROOTCERTIFICATE" -KeyExportPolicy Exportable ` -HashAlgorithm sha256 -KeyLength 2048 ` -CertStoreLocation "Cert:\CurrentUser\My" -KeyUsageProperty Sign -KeyUsage CertSign <#   We are generation a Client certificate from root certificate. After you are creating this go to certmgr.msc(run this command from command propmpt) #> New-SelfSignedCertificate -Type Custom -DnsName REBELCLIENT -KeySpec Signature ` -Subject "CN=CLIENTCERTIFICATE" -KeyExportPolicy Exportable ` -HashAlgorithm sha256 -KeyLength 2048 ` -CertStoreLocation "Cert:\CurrentUser\My" ` -Signer $cert -TextExtension @( "2.5.29.37={text}1.3.6.1.5.5.7.3.2" ) Get-ChildI

The specified pull subscription is not configured with a synchronization agnent job.(.Net sqlclient Data Provider)

Image
I got this below error while i am working in Merge Publication in sql server. I have configured merge publication as pull publication in the environment,so obviously the merge agent job created under subscriber server, but suddenly it stopping rolling forward changes to the subscriber and throwing the below mentioned error.     If i try to click on the Start button the above error is coming up. The issue came up because some added a new step in the job properties of steps section and deleted that later, afterwards this issue occuring. Workaround: Delete the exising Merge agent job from subscriber server before you are running the below query. --run this in subscriber server under pull subscription exec sp_addmergepullsubscription_agent   @publisher = 'RAMESH' ,--> Publisher server name here   @publisher_db = 'sample' ,-->Publisher database name here   @publication = 'MergePub_Sample' ,-->Publication name her

Msg 2732, Sev 16, State 1, Line 472 : Error number 3013 is invalid. The number must be from 13000 through 2147483647 and it cannot be 50000. [SQLSTATE 42000] Job 'JobNameHere' : Step 2, 'StepNamehere' : Began Executing 2019-04-25 02:06:07

To day i got an error in one of my clients environment. One of the SQL Server Agent jobs got failed with the below error message. Msg 2732, Sev 16, State 1, Line 472 : Error number 3013 is invalid. The number must be from 13000 through 2147483647 and it cannot be 50000. [SQLSTATE 42000]  Job 'JobNameHere' : Step 2, 'StepNamehere' : Began Executing 2019-04-25 02:06:07 When i first go through the error, i thought it could be code issue which is written in a particular stored procedure of job. What this job is doing it is restoring the backups from source. So wherever it is restoring in that server in whichever drive the log file is placing(.LDF) , the free space in that particular drive is very less, increasing the log file drive(wherever LDF file is placing) space resolved the issue.

Getting the Cluster info through power shell from the cluster nodes.

<#You can pass multiple computer names or server names to the computer parameter name. But  dont provide values in between ""#> Invoke-Command  ` -ComputerName   SERVER1 , SERVER2 , SERVER3  ` -ScriptBlock { Get-ClusterGroup | Format-Table   -AutoSize Get-ClusterResource | Where-Object  {( $_ . ResourceType   -like   "*SQL SERVER*" )   -or  ( $_ . ResourceType   -like   "*Generic*" )} | Format-Table   -AutoSize } | Format-Table   -AutoSize