Comments
Sort by recent activity
There, the message above shows what i try to explain as <SQUARE> [image] / comments
There, the message above shows what i try to explain as <SQUARE>
Hi,
I did a upgrade to test and check the settings you asked for.
1: v4 - Everything worked, saved registry
2: upgraded to v5 - Ran the same job, everything worked, saved registry
3: Tested to send mail from the GUI, failed with authentication unsucsessfull, wrote the same passord as had been there before and tested again, mail worked from the GUI
4: Ran the same job again, FAILED on mail send with authentication unsucsessful, saved registry
I then compared the 3 registry files I had saved. Everything except the password were identical. In step 1&2 the password was identical, but in step 4, which was after I had added the same password, there was 1 slight difference in the ending of the password.
I then did another test on another server.
While on v4 i set the password for email to REDGATE in the registry this became: ’T"G‚EE
I then upgraded to v5, password in registry: ’T"G‚EE
I then went into the GUI, and typed in PASSWORD in the password field, and then checked registry: <SQUARE>T"G<SQUARE>‚EE
<SQUARE>=couldnt cut'n'paste this value, but it is this square box kinda symbol, that you sometimes see if you open a .exe file in a text editor or such. Or when I look at the preview of this posting, there are a few of those "boxes" below here, between the , and <:
‚<
I tried cut'n'paste the encrypted password from a server that workes into a server that fails, that solves the problem of mailsending, as long as I dont try updating in the GUI again. [image]
So, it seems like it is the GUI that messes up the password....
-Magne / comments
Hi,
I did a upgrade to test and check the settings you asked for.
1: v4 - Everything worked, saved registry
2: upgraded to v5 - Ran the same job, everything worked, saved registry
3: Tested to send...
< / comments
<
Some more information to add to the confusion:
On one of the servers that mail WORKED on yesterday I still went in and checked the email options. Test failed due to authentication. I punched in the correct password (it hadnt been touched since long before the upgrade to v5, and has worked all the time), test sent email from the GUI. Worked fine.
Started the job on the server. It failed with exit code 151!!!!!!!!!!!
Something seems to be really sick....
..help? [image] / comments
Some more information to add to the confusion:
On one of the servers that mail WORKED on yesterday I still went in and checked the email options. Test failed due to authentication. I punched in the...
A small correction, I see now that some of the old installations that have been upgraded also fails on mail sending, but not all of them.
They all use the same account for mail sending, and all of them send mail perfectly when tested from the SQL Backup GUI Options for setting up mail.
Testing backup from the GUI also fails with the same message on mail sending.
So, to summarize:
Mail sending from the mail setup in the GUI works for all servers
Mail sending from the scheduled jobs or from the Backup in the GUI fails for some
All use the same smtp server/account++
-Magne / comments
A small correction, I see now that some of the old installations that have been upgraded also fails on mail sending, but not all of them.
They all use the same account for mail sending, and all of ...
Yup, patched version worked... / comments
Yup, patched version worked...
Here is the value of logical_device_name for a backup:
Red Gate SQL Backup (4.6.0.815):0000001C26A6000000000006797080000000000000001B6D0203
The report for that same backup was mailed to me and had this information:
BACKUP DATABASE successfully processed 14758649 pages in 7020.288 seconds (17.221 MB/sec).
It came as a success, without warnings.
The exact same information is in the log file.
In the GUI the compression speed is reported as 0. / comments
Here is the value of logical_device_name for a backup:
Red Gate SQL Backup (4.6.0.815):0000001C26A6000000000006797080000000000000001B6D0203
The report for that same backup was mailed to me and had ...
When I was in contact with MS this cumulative patch was the only solution.
They did not say anything about SP5. There was a hotfix for this problem alone, but that was only available in a few languages.
The server we've been running on has not had any problems yet, but it is a test-server. Though it is used daily, quite intensively.
-Magne / comments
When I was in contact with MS this cumulative patch was the only solution.
They did not say anything about SP5. There was a hotfix for this problem alone, but that was only available in a few langu...
yet another update. there seems to be a problem obtaining just the hotfix.
The hotfix for only this error is only available for French, German, and japanese. If on an English version as we are, the only option is the cumulative update that I wrote about earlier, which worked here.
-Magne / comments
yet another update. there seems to be a problem obtaining just the hotfix.
The hotfix for only this error is only available for French, German, and japanese. If on an English version as we are, the...
This cumulative update solved the problem. [image]
Thanks for your help!
-Magne / comments
This cumulative update solved the problem.
Thanks for your help!
-Magne