The error that the other server returned was: 550 550 Mailbox unavailable or access denied – <example@comcast.com> (state 13).
I was sending an old contact an email, and got this in my bounceback, and NO, the email address in my example is not the email address I was sending to. The fix was simple enough, I had to change the address to the .net TLD and was then able to resend the message.
Restore of database ‘NEWDB’ failed. (Microsoft.SqlServer.Management.RelationalEngineTasks) ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: BACKUP LOG cannot be performed because there is no current database backup. (Microsoft.SqlServer.SmoExtended) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.2100.60+((SQL11_RTM).120210-1917+)&LinkId=20476
Lets take a look in the SQL Server error log, to do so:
In Object Explorer, expand a server, expand Management, and then expand SQL Server Logs.
Right-click a log and click View SQL Server Log.
The errors (combined below for readability) generated for this is not much more helpful.
Date 11/20/2012 11:56:40 AM
Log SQL Server (Current – 11/20/2012 12:03:00 AM)
Source Backup
Message
Error: 3041, Severity: 16, State: 1.
BACKUP failed to complete the command BACKUP LOG NEWDB. Check the backup application log for detailed messages.
As it turns out, I also had the warning of ‘A tail-log backup of the source database will be taken. View this setting on the Options page.’ This was also a just created database. When I unchecked the box for ‘Take tail-log backup before restore’ under the ‘Tail-Log backup’ section I was then able to run my restore and get past this error. This is the first time I have run into this error, I am unsure if this is a change with SQL 2012.
Are you migrating SQL users? I recommend migrating their SID’s as well. There is this article on MSDN. The sum of it is to run this:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 |
USE master GO IF OBJECT_ID ('sp_hexadecimal') IS NOT NULL DROP PROCEDURE sp_hexadecimal GO CREATE PROCEDURE sp_hexadecimal @binvalue varbinary(256), @hexvalue varchar (514) OUTPUT AS DECLARE @charvalue varchar (514) DECLARE @i int DECLARE @length int DECLARE @hexstring char(16) SELECT @charvalue = '0x' SELECT @i = 1 SELECT @length = DATALENGTH (@binvalue) SELECT @hexstring = '0123456789ABCDEF' WHILE (@i <= @length) BEGIN DECLARE @tempint int DECLARE @firstint int DECLARE @secondint int SELECT @tempint = CONVERT(int, SUBSTRING(@binvalue,@i,1)) SELECT @firstint = FLOOR(@tempint/16) SELECT @secondint = @tempint - (@firstint*16) SELECT @charvalue = @charvalue + SUBSTRING(@hexstring, @firstint+1, 1) + SUBSTRING(@hexstring, @secondint+1, 1) SELECT @i = @i + 1 END SELECT @hexvalue = @charvalue GO IF OBJECT_ID ('sp_help_revlogin') IS NOT NULL DROP PROCEDURE sp_help_revlogin GO CREATE PROCEDURE sp_help_revlogin @login_name sysname = NULL AS DECLARE @name sysname DECLARE @type varchar (1) DECLARE @hasaccess int DECLARE @denylogin int DECLARE @is_disabled int DECLARE @PWD_varbinary varbinary (256) DECLARE @PWD_string varchar (514) DECLARE @SID_varbinary varbinary (85) DECLARE @SID_string varchar (514) DECLARE @tmpstr varchar (1024) DECLARE @is_policy_checked varchar (3) DECLARE @is_expiration_checked varchar (3) DECLARE @defaultdb sysname IF (@login_name IS NULL) DECLARE login_curs CURSOR FOR SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM sys.server_principals p LEFT JOIN sys.syslogins l ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name <> 'sa' ELSE DECLARE login_curs CURSOR FOR SELECT p.sid, p.name, p.type, p.is_disabled, p.default_database_name, l.hasaccess, l.denylogin FROM sys.server_principals p LEFT JOIN sys.syslogins l ON ( l.name = p.name ) WHERE p.type IN ( 'S', 'G', 'U' ) AND p.name = @login_name OPEN login_curs FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin IF (@@fetch_status = -1) BEGIN PRINT 'No login(s) found.' CLOSE login_curs DEALLOCATE login_curs RETURN -1 END SET @tmpstr = '/* sp_help_revlogin script ' PRINT @tmpstr SET @tmpstr = '** Generated ' + CONVERT (varchar, GETDATE()) + ' on ' + @@SERVERNAME + ' */' PRINT @tmpstr PRINT '' WHILE (@@fetch_status <> -1) BEGIN IF (@@fetch_status <> -2) BEGIN PRINT '' SET @tmpstr = '-- Login: ' + @name PRINT @tmpstr IF (@type IN ( 'G', 'U')) BEGIN -- NT authenticated account/group SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' FROM WINDOWS WITH DEFAULT_DATABASE = [' + @defaultdb + ']' END ELSE BEGIN -- SQL Server authentication -- obtain password and sid SET @PWD_varbinary = CAST( LOGINPROPERTY( @name, 'PasswordHash' ) AS varbinary (256) ) EXEC sp_hexadecimal @PWD_varbinary, @PWD_string OUT EXEC sp_hexadecimal @SID_varbinary,@SID_string OUT -- obtain password policy state SELECT @is_policy_checked = CASE is_policy_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name SELECT @is_expiration_checked = CASE is_expiration_checked WHEN 1 THEN 'ON' WHEN 0 THEN 'OFF' ELSE NULL END FROM sys.sql_logins WHERE name = @name SET @tmpstr = 'CREATE LOGIN ' + QUOTENAME( @name ) + ' WITH PASSWORD = ' + @PWD_string + ' HASHED, SID = ' + @SID_string + ', DEFAULT_DATABASE = [' + @defaultdb + ']' IF ( @is_policy_checked IS NOT NULL ) BEGIN SET @tmpstr = @tmpstr + ', CHECK_POLICY = ' + @is_policy_checked END IF ( @is_expiration_checked IS NOT NULL ) BEGIN SET @tmpstr = @tmpstr + ', CHECK_EXPIRATION = ' + @is_expiration_checked END END IF (@denylogin = 1) BEGIN -- login is denied access SET @tmpstr = @tmpstr + '; DENY CONNECT SQL TO ' + QUOTENAME( @name ) END ELSE IF (@hasaccess = 0) BEGIN -- login exists but does not have access SET @tmpstr = @tmpstr + '; REVOKE CONNECT SQL TO ' + QUOTENAME( @name ) END IF (@is_disabled = 1) BEGIN -- login is disabled SET @tmpstr = @tmpstr + '; ALTER LOGIN ' + QUOTENAME( @name ) + ' DISABLE' END PRINT @tmpstr END FETCH NEXT FROM login_curs INTO @SID_varbinary, @name, @type, @is_disabled, @defaultdb, @hasaccess, @denylogin END CLOSE login_curs DEALLOCATE login_curs RETURN 0 GO |
This awesome stored procedure is created, you can then run it as so:
|
1 |
EXEC sp_help_revlogin |
The output is what would be needed to create the users, and their associated SID’s on a separate instance of SQL server. See http://support.microsoft.com/kb/918992
You can also pull the details from a single database, for example:
|
1 |
select name, sid from syslogins where password is not null and name != 'sa' |
You can then use this output to manually recreate the logins:
|
1 |
exec sp_addlogin @loginame='user', @passwd='password', @sid=sid |
I personally see this as useful when I do not have access to the source installation to run the first set of scripts, and am only supplied a backup.
I received the error of “php Warning: Cannot modify header information”, and found the fix is to update my php.ini to include this:
|
1 |
output_buffering = On |
I ‘could’ also set the variable in an include page, if my site was running PHP as a CGI.
If you need to test a server using a domain name, but can not repoint the domain to test, you can force your local machine to resolve the domain name to the IP address of your choice. You do this using the hosts file, on Windows, or the resolv.conf file on a linux OS. This is going to be OS specific, find the directions below for your OS.
COMING SOON!
Start -> All Programs -> Accessories -> Notepad
Right click and run as administrator.
File -> Open
%SystemRoot%\system32\drivers\etc\hosts
You may need to type in the name hosts again.
Here you can edit. The format is rather clear. For each line you have an IP followed by white space, followed by each FQDN you want to resolve to this IP. This list of FQDN’s need to be white space delimited. Save the file. Flush your DNS cache:
|
1 |
ipconfig /flushdns |
If you are testing with a web browser, you may need to take additional steps to circumvent DNS caching within the program.
If you are going to be editing this file often, you can also make a shortcut as so:
Create a shortcut in a folder of your choice.
For the “Type the location of the item” field, put in the following:
C:\Windows\System32\notepad.exe C:\Windows\System32\drivers\etc\hosts
Click Next. On this screen I just title the shortcut ‘hosts’.
Drag this shortcut to your task bar.
Right click on the notepad icon that shows, then right click on the notepad icon in the popup bubble. From there go to Properties.
On the Shortcut tab, go to Advanced. Check the box for Run as Administrator.
Click OK, Click OK. Now when you click on that link it will prompt you to run Notepad as Administrator and allow you to edit and save the hosts file very easily.
Also, COMING SOON!
COMING SOON!
COMING SOON!
I want a ONE liner to migrating MySQL users between servers. We know that migrating databases is easy enough using mysqldump, but migrating users from one MySQL instance or server to separate one can be annoying. Based on well known export commands, here is a neat little piped set of commands that you can run on the source DB server. The command will generate all the GRANT statements that you can simply run on the destination DB server.
|
1 |
mysql -u <ROOTUSERNAME> -B -N -p<ROOTPASSWORD> -e "SELECT user, host FROM user" mysql | awk '{print "mysql -u <ROOTUSERNAME> -p<ROOTPASSWORD> -B -N -e\"SHOW GRANTS FOR " $1 "@" $2 "\""}' |
If you are logged in as root user and do NOT need to supply user and password:
|
1 |
mysql -B -N -e "SELECT user, host FROM user" mysql | awk '{print "mysql -B -N -e\"SHOW GRANTS FOR " $1 "@" $2 "\""}' |
Hey, lets go two better, lets run the output, and add semicolons at the end of the lines to make the output appropriate to run on the destination server.
|
1 |
mysql -B -N -e "SELECT user, host FROM user" mysql | awk '{system( "mysql -B -N -e\"SHOW GRANTS FOR " $1 "@" $2 "\"")}' | sed 's/$/;/' |
The beauty of this is that you need not know the passwords for any of the mysql user accounts and are then given one block of output, instead of the commands to run to get the grants.
*Migrating all databases except mysql and information_schema:
|
1 |
mysql -u <MYSQLROOTTUSERNAME> -p<MYSQLROOTPWD> -B -N -e"SHOW DATABASES;" | grep -v mysql | grep -v information_schema | xargs mysqldump -u <MYSQLROOTTUSERNAME> -p<MYSQLROOTPWD> --databases > mysqldbdump.sql |
Originaly found on http://jasonbos.co/migrating-mysql-users-from-one-server-to-anot
I recently came across a scenario where I needed to have a mailto: link include additional details, and particularly an email address in the cc field. You can configure an HTML mailto: link to include a number of fields:
The Mailto: Link
The Mailto: Link is a variation of the standard HTML Hyperlink. It invokes the browser to send an email when the ‘href’ attributes value starts with ‘mailto:’ as below.
|
1 |
<a href="mailto:">Email</a> |
To: – Setting the email recipient
The To: field is the only required field of a Mailto: link. This is the email address that the generated email will be sent to.
|
1 |
<a href="mailto:user@example.com">Email</a> |
If you wish to add multiple recipients to the To: field (or the CC: and BCC: fields as shown below) separate the addresses with commas (e.g. admin@example.com,end_user@example.com).
CC: – ‘Carbon Copy’ for adding additional recipients
Note: When adding items to your mailto: link make sure to add a question mark (?) after the ‘To:’ field.
|
1 |
<a href="mailto:user@example.com?cc=other_user@example.com">Email</a> |
BCC: – ‘Blind Carbon Copy’ for adding hidden recipients
You can also add recipients to the email who will be hidden from the To: and CC: recipients within the email message, by using the BCC: field. If you have already added a CC: (or any other element) to your mailto: link, you should include an ampersand (&) before each additional item.
|
1 |
<a href="mailto:user@example.com?cc=other_user@example.com&bcc=admin@example.com">Email</a> |
Subject: – Adding subjects to your emails
The Subject: field in your mailto: link will allow you to set the emails subject.
|
1 |
<a href="mailto:user@example.com?cc=other_user@example.com&bcc=admin@example.com&subject=Test%20Email">Email</a> |
Note: A mailto: link can not contain spaces. When adding a Subject: or Body: field use ‘%20’ instead.
Body: – Making an email template
The final variable of a mailto: link is the Body: attribute. This allows you to set a specific message within the body of the message. You can enter a line such as, “I would like to unsubscribe from this poop.″ with the following:
|
1 |
<a href="mailto:recipient@domain.com?cc=other@domain.com&bcc=hidden@domain.com&subject=Test%20Email&body=I%20would%20like%20to%20unsubscribe%20from%20this%20poop.">Email</a> |
Summary
A fully formed mailto: link can be very useful! Use it, and be more awesome!!
SmarterStats, and you. I ♥ SmarterStats, from a usability standpoint as well as from an administrator/troubleshooter standpoint. The latest iteration is 7.6.4682, as of this writing. Release notes are found here. After the installation, including the requirement for .NET 4, it will auto open the Getting Started page, likely at http://localhost:9999/GettingStarted.htm. It seems that in this version, and possibly prior versions, there is a Getting Started video tour. I am going to chose to Begin Setup. The screen we are welcomed with is the License Setup Screen. If you have a license, go ahead and put it in now. If not, that is fine. A license can be added into the system after the setup is complete.
In my example, I am deciding to run SmarterStats as the free edition. After clicking Next, the Create System Administrator screen is shown:
As you can see the password does have some requirements.
This does allow one to use the password of ‘admin’ sans quotes. I recommend against this in a production environment. Making our way to the Next screen, we have the Default System Settings:
The SmarterLogs Path shown is the default, and quite honestly my preference. This path is important when troubleshooting issues to a specific site. The Time Zone setting seems to load based on the local time, and can be changed later on. I believe we also get the option to set this different per site. Our final screen is the Default SMTP Settings screen. Here you can configure how SmarterStats sends email messages. I usually think of this in terms of reports,standard and custom. This can be configured after the setup is complete as well. Once ready click Finish. This article will be updated with links to specific tasks.
This article is essentially a combination of two articles I had read online. One made it easy to find the errors and the other made it easy to find the fix, but I wanted one place where I could find BOTH. What do you need in place in order to use xp_cmdshell? I warn you, there are obvious security risks and implications for going this route. (I’m not recommending usage of xp_cmdshell in general, and frankly have no clue how to use it, but you don’t need to know how to use it to enable it) We first need to think about what happens here, from an architectural level:
A user who has logged in to SQL Server executes xp_cmdshell. For this, SQL Server need to spawn a process in Windows. A process in Windows need to execute in a Windows user account. How does SQL Server know what Windows account is to be used? If the SQL Server login who is executing xp_cmdshell is sysadmin, then SQL Server will use the service account (it will not “pretend to be somebody else” or emulate another user). However, if the login is not sysadmin, then one would need to configure what Windows account to be used (using sp_xp_cmdshell_proxy_account). Note that this configuration is the same for all non-sysadmins. But there’s a little bit more to it than a single setting. Below is an outline of what needs to be done. Step 2 and 3 are only needed if the one who is to execute xp_cmdshell isn’t sysadmin. Note that the steps don’t have to be performed in the order listed below.
We need to allow usage of xp_cmdshell in general (on 2005 or 2008). Use “Surface Area Configuration” or sp_configure to perform this. We need to have a user in the master database which has execute permission on xp_cmdshell. If you are uncertain about the difference between logins and users, you should read up about it in BOL. We need to say what Windows account should be used when a non-sysadmin user is executing xp_cmdshell.
For users that are not members of the sysadmin role on the SQL Server instance, as mentioned above, you need to do the following actions to grant access to the xp_cmdshell extended stored procedure.
Below are the Errors thrown and the TSQL script correcting said error, that enables this:
(1) Enable the xp_cmdshell procedure
*Msg 15281, Level 16, State 1, Procedure xp_cmdshell, Line 1 SQL Server blocked access to procedure ‘sys.xp_cmdshell’ of component ‘xp_cmdshell’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘xp_cmdshell’ by using sp_configure. For more information about enabling ‘xp_cmdshell’, see “Surface Area Configuration” in SQL Server Books Online.*
Fix:
|
1 2 3 |
EXEC sp_configure 'xp_cmdshell', 1 RECONFIGURE GO |
(2) Create a login for the non-sysadmin user that has public access to the master database
*Msg 229, Level 14, State 5, Procedure xp_cmdshell, Line 1 The EXECUTE permission was denied on the object ‘xp_cmdshell’, database ‘mssqlsystemresource’, schema ‘sys’.*
Fix:
|
1 2 3 |
USE master CREATE LOGIN RoseBush WITH PASSWORD = 'securepassword' CREATE USER RoseBush FROM LOGIN RoseBush |
(3) Grant EXEC permission on the xp_cmdshell stored procedure
*Msg 229, Level 14, State 5, Procedure xp_cmdshell, Line 1 The EXECUTE permission was denied on the object ‘xp_cmdshell’, database ‘mssqlsystemresource’, schema ‘sys’.*
Fix:
|
1 |
GRANT EXECUTE ON xp_cmdshell TO RoseBush |
(4) Create a proxy account that xp_cmdshell will be run under using sp_xp_cmdshell_proxy_account
*Msg 15153, Level 16, State 1, Procedure xp_cmdshell, Line 1 The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the ‘##xp_cmdshell_proxy_account##’ credential exists and contains valid information.*
Fix:
|
1 |
EXEC sp_xp_cmdshell_proxy_account 'Domain\WindowsUserAccount','password' |
Leverage browser caching
With a note of: (expiration not specified)
To deal with this, I added the following to my .htaccess file:
|
1 2 3 4 5 6 |
<FilesMatch "\.(ico|jpg|jpeg|png|gif|js|css|swf|woff|ICO|JPG|JPEG|PNG|GIF|JS|CSS|SWF|WOFF)$"> <IfModule mod_expires.c> ExpiresActive on ExpiresDefault "access plus 30 days" </IfModule> </FilesMatch> |
This is a modified version of what I saw recommended. The original as I found it was:
|
1 2 3 4 5 6 7 8 |
<FilesMatch "\.(ico|jpg|jpeg|png|gif|js|css|swf)$"> <IfModule mod_expires.c> ExpiresActive on ExpiresDefault "access plus 30 days" </IfModule> Header unset ETag FileETag None </FilesMatch> |
However I had a plugin that added the ‘Header unset ETag’ and ‘FileETag None’ lines. I found the code here, and you can read up on mod_expires here. It is good to note that although the message recommends at least 7 days, Google has a best practices guide found here that recommends 30 days as a minimum.