I’m no guru at Linux and MySQL but I get around okay. I looked up the “Loading…” thing first but it’s too vague of a search with too many possibilities. Eventually I found that half of the mboxgroup databases were corrupted along with some of the Zimbra database tables. Every attempt to check or repair would just sit there spinning its wheels and never complete they were so jacked up. Fortunately I made a copy of the VM’s after the host did that last reset and decided it was best to go back to the copy I made. That night with all of the other VM’s powered off I started the Zimbra server and started repairing it while keeping the users off because it the corruption is likely to spread when in use. I say that because after the restore there was only one mboxgroup database that had a problem and this time I was able to do a dump from it. Good thing too because the repair didn’t work and said I was using the wrong engine. The data was really trashed.

NOTE: Some commands are word wrapped to fit.

First off you should know your passwords for the MySQL operations. If not you’ll need to reset them as shown from http://blog.aionsolution.com/category/zimbra/ as follows.

Updating Mailbox MySQL Database Passwords

It is necessary to run the password update commands as the zimbra user.

# su - zimbra

Make sure the mailbox mysql database is running. Note that the actual process id (pid) will vary.

 $ mysql.server status
 mysql is running with pid 23830

If that fails to find a running mysql, verify that the mailbox mysqld does not appear in the process list, and then start it.

$ ps a | grep mysqld.*my.cnf
$ mysql.server start

Update the mysql root password.

$ zmmypasswd --root newrootpass

Update the zimbra mysql password.

$ zmmypasswd newpass

Updating Logger MySQL Database Passwords

It is necessary to run the password update commands as the zimbra user.

# su - zimbra

Make sure the logger mysql database is running. Note that the actual process id (pid) will vary.

$ logmysql.server status
  mysql is running with pid 23830

If that fails to find a running mysql, verify that the mailbox mysqld does not appear in the process list, and then start it.

$ ps a | grep mysqld.*my.logger.cnf
$ logmysql.server start

Update the logger mysql root password.

$ zmmylogpasswd --root newrootpass

Update the logger zimbra mysql password.

$ zmmylogpasswd newpass

Now you can check to see what is damaged.

Change to the user zimbra by the su command if you skipped the previous password changes.

$ su zimbra

Check for databases for errors:

$ /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf
  -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=your password

 This will show you something like this: mboxgroup10.mail_item
 error    : Corrupt
 zimbra.jiveID
 warning  : 1 client is using or hasn't closed the table properly
 zimbra.jiveOffline
 warning  : 1 client is using or hasn't closed the table properly
 zimbra.jiveRoster
 warning  : 1 client is using or hasn't closed the table properly
 zimbra.jiveUserProp
 warning  : 1 client is using or hasn't closed the table properly

I checked each of these tables individually:

$ mysql -e “check table mboxgroup10.mail_item”
to
$ mysql -e “check table zimbra.jiveUserProp”

1. Load some mysql configuration into shell variables (i.e. $mysql_socket and $mysql_root_password; note that you will use these again in step 3)
2. Make a list of the existing databases
3. Create a directory to hold the SQL dumps
4. Generate the SQL dumps from the database list

1.  $ source ~/bin/zmshutil ; zmsetvars
2.  $ mysql --batch --skip-column-names -e "show databases" | grep -e mbox
            -e zimbra > /tmp/mysql.db.list
3.  $ mkdir /tmp/mysql.sql
4.  $ for db in `cat /tmp/mysql.db.list`; do
       ~/mysql/bin/mysqldump $db -S mysql_socket -u root
            --password=$mysql_root_password > tmp/mysql.sql/$db.sql
       echo "Dumped $db"
       done

Note: If you encounter any mysql errors while dumping the databases, start over by re-editing /opt/zimbra/conf/my.cnf, incrementing the value for innodb_force_recovery by one, and restarting mysqld. The maximum recovery level is 6. Please see MySQL’s Forcing InnoDB Recovery guide for more information.

Note: An error of “bash: /tmp/mysql.sql/$db.sql: ambiguous redirect” probably indicates your using an apostrophe or single quote ‘ rather than a tick ` — which is one the same key as the tilde ~ .

Note: Do not reboot the machine, as some Operating Systems will remove all contents in the /tmp directory during the reboot sequence, i.e. your /tmp/mysql.sql will be removed.

Now start repairing each one:

$ mysql -e “repair table mboxgroup10.mail_item”
$ mysql -e “repair table zimbra.jiveUserProp”

When all are done and then go back and test them again.

In my case the mboxgroup10 database couldn’t be repaired. That’s where the data dump comes in handy. So I did this:

$ mysql DROP DATABASE mboxgroup10
$ mysql CREATE DATABASE mboxgroup10
$ mysql mboxgroup10 < mboxgroup10.sql

- Cory L Curtis
- 2012-05-18

Related Posts:

• No Related Posts

Go to the Office Button / Excel Options / Advanced, and scroll all the way down to the General section. There you will see the “Ignore other applications that use Dynamic Data Exchange (DDE)” setting checked. Uncheck the box, click OK to apply, and you’re good to go

The window dialog looks like this:

- Cory L. Curtis
- 2012-01-09

Related Posts:

• No Related Posts

UPDATE:
I was wrong, there is someone out there with another solution. Worked for me. My info below works too but I suspect this links solution is more secure.
See http://www.pmdconsulting.biz/blog/plugin-upgrade-failed-in-wordpress-using-iis-7/

This plugin update problem on IIS7 with WordPress has been one of those plagues that has been bugging me for a while but I never had the time to resolve it until now. I couldn’t find an answer anywhere so you won’t find any links in this one to other sources.
The error is
Unpacking the update…

Plugin update failed.

To start with you’ll need to add two different accounts to the afflicted sites folders. If you’re going to upgrade WordPress itself then you’ll need to add them to the root of the site as well. One is “IUSR” and the other is “Network Service”. These need permissions to modify but if there is a folder that the administrative tools need to create then the “Network Service” account needs full access. If updating plugins is your only goal then they need to added to the “wp-content” folder only.

If you’re going to do automatic upgrades to WordPress as a whole then you need to open the IIS console, go to the Application Pool, and click on the site you’re working on. On the upper right corner click “Set Application Pool Defaults”. Look for “Process Model”, then “Identity”. Select the drop-down and change the account there to “Network Service” and save it.

The biggest culprit of the problem is IIS caching. In the IIS console go to the website we’re working on and highlight it. Now double click “Output Caching”. Click “Edit Feature Settings” on the top right and remove the check box on “Enable Cache” to disable it, click on OK. Restart IIS.
You should now be able to run all of your updates. Maybe. But if your paranoid like me then set it all back the way it was until your ready to do updates again.

As always, if I got something wrong please tell me.
- Cory L Curtis
- 2011-12-09

Related Posts:

• No Related Posts

The purpose of this article is to explain how to setup the “Send As” feature in Microsoft’s Office 365 web services. This is for when you would like an employee to be able to send an email for you so that it is as if you sent it yourself. You would of course only allow this kind of privilege only to someone you trust to act on your behalf in sending email for you. Anyone who replies to one of these emails sent on your behalf would be sending it directly to your email address and not the trustee because to the original recipient, they don’t know that you didn’t really send it and that your trustee did. This is different than “Send on behalf of” where you would know that the trustee sent it.

Step 1:
To start, you need to have Windows PowerShell installed. Preferably 2.0 but version 1.0 works as well. If you have Windows 7 or 2008 Server R2 then you should already have it. If not, then get it.
http://support.microsoft.com/kb/968929/en-us

Step 2:
Open PowerShell with the Administrator account by going to the main menu. The path to it is “All Programs\Accessories\Windows PowerShell\Windows PowerShell (x86) or Windows PowerShell. It doesn’t matter which one. Right Click it and select “Run As Administrator”.
At the command line type or paste: (right click to paste in the command line shell)
get-executionpolicy
press enter to execute. It should say “RemoteSigned”. If not then type or paste:
set-executionpolicy remotesigned
and press enter. It will show the following;

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust. Changing the execution policy might expose
you to the security risks described in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes [N] No [S] Suspend [?] Help (default is "Y"):

Type “Y” and press enter to change the Execution Policy to RemoteSigned.
This makes changes to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell in the registry.
Now we’re ready for the good stuff.

Step 3:
In the command line type or paste:
$LiveCred = Get-Credential

This will open a logon dialog “Windows PowerShell Credential Request”. Enter the email address of a user account that is an administrator for your Office 365 account and its password. This stores these credentials for doing the “Send As’ setup.

Step 4:
Type or paste this in the command line
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Step 5:
(If you installed the “Microsoft Online Services Module” then you can skip this step. If you’re not sure then do it anyhow.)
Type or paste in the command line
Import-PSSession $Session

This downloads the scripts for administrating Office 365 from PowerShell.

Step 6:
Now to set your permissions for a specific user. Type the folowing but substitute your “Send As” account and the trustee account.
Add-RecipientPermission -AccessRights SendAs -Trustee
Like this:
Add-RecipientPermission sendas@yourdomain.com -AccessRights SendAs -Trustee trustee@yourdomain.com

Step 7:
When your done you can end the session by typing or pasting
Remove-PSSession $Session

Also these commands are useful
View Send As permissions :
Get-RecipientPermission - Trustee

View Send As permission on a specific recipient :
Get-RecipientPermission

View all Send As permissions you’ve configured in your organization :
Get-RecipientPermission | where {($_.Trustee -ne 'nt authority\self') -and ($_.Trustee -ne 'null sid')}

Revoke Send As permission :
Remove-RecipientPermission -AccessRights SendAs -Trustee

For more detail see the following:
http://207.46.16.237/en-us/140/cc952756.aspx
http://207.46.16.237/en-us/140/cc952755.aspx
http://207.46.16.237/en-us/140/ff852815.aspx
Single Sign-on :
http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652560.aspx

If there are any errors in this information please notify me.
Contact Form

- Cory L Curtis
- 2011-12-01

UPDATE: 2012-02-20
I found a link to do send as without using PowerShell to configure it. The “New” button was only available with my admin logon but even as an admin I couldn’t connect to another account to set it up. If you have some time to kill you might give it a try.
Office 365: Grant Send As Permission Without Using PowerShell P1 Plan

Related Posts:

• No Related Posts

Related Posts:

• 24 Hour Catastrophic Technoogie Failure

I don’t know where the folder is located on a Mac but in Windows 7 it is here.
C:\Users\(Your User Profile)\AppData\Roaming\Adobe\Common\Media Cache Files

You could make a shortcut to the folder or if you’re real ambitious you could run a vbscript in the task manager once a week to delete cache files older than 60 days or so.
I don’t remember where I got this script from but here ‘s one that works well. Be careful!
- Cory L Curtis
- 2011-08-11




‘ ————————————————————-
‘ Deletes all files in the given path that are older than the number of days set on line 7
‘ 365 = 1yr, 183 = One Half Year
‘ ————————————————————-
Set objFSO = CreateObject(“Scripting.FileSystemObject”)
strFolder = “C:\Users\(Your User Profile)\AppData\Roaming\Adobe\Common\Media Cache Files\” ‘[[[ Don't forget the back-slash at the end ]]]
strDateMinus = DateAdd(“d”, -60, Date) ‘[[[ Number of Days in Calculation ]]]

Set objStartFolder = objFSO.GetFolder(strFolder)
Set colFiles = objStartFolder.Files
For Each objFile In colFiles
If objFile.DateLastModified < strDateMinus Then
objFSO.DeleteFile objFile.Path,True
End If
Next

ProcessAllFiles objStartFolder
ProcessAllFolders objStartFolder

Sub ProcessAllFiles(Folder)
For Each SubFolder In Folder.SubFolders
Set objFolder = objFSO.GetFolder(Subfolder.Path)
Set colFiles = objFolder.Files
For Each objFile In colFiles
If objFile.DateLastModified < strDateMinus Then
objFSO.DeleteFile objFile.Path,True
End If
Next
ProcessAllFiles Subfolder
Next
End Sub

Sub ProcessAllFolders(Folder)
For Each SubFolder In Folder.SubFolders
Set objFolder = objFSO.GetFolder(Subfolder.Path)
Set colFolders = objFolder.SubFolders
For Each objSubFolder In colFolders
If objSubFolder.Size = 0 Then
objFSO.DeleteFolder objSubFolder.Path,True
End If
Next
ProcessAllFolders Subfolder
Next
End Sub

Related Posts:

• No Related Posts

I have no idea what really causes this. I saw solutions that would have you delete every registry key that matched the KB number that won’t install. One recommended a reinstallation of the operating system. NO WAY! Especially not on a server. The one that made the most sense and worked for me was to manually install the update that was failing.

Good luck finding the individual updates on Microsoft’s website. It’s a convoluted effort at best, but be persistent and you’ll eventually find what you’re looking for.

- Cory L. Curtis
- 2011-07-28

Related Posts:

• No Related Posts

They were using a Linksys E3000. The E3000 supports N speeds in both the 2.4 GHz and 5 GHz band and for whatever reason the HP iPrint service doesn’t work on it unless you disable the 5 GHz mode. Once you do that, the iPad sees the HP iPrint service.

Here’s a screenshot of the Linksys E3000 page to disable the 5 GHz band.

- Cory L. Curtis
- (2011-06-30)

Related Posts:

• No Related Posts

The Answer : http://www.warriorforum.com/programming-talk/400115-php-5-3-6-just-killed-my-site-help.html
They make a reference to another site but there is no link to it.
Found it here though : http://www.cjaymead.co.uk/wordpress/plugins/problem-with-wordpress-automatic-upgrade-after-upgrade-to-php-5-3/

We too were using “WordPress Automatic Upgrade”. I removed the plugin folder and Wah La. Back in business.

- Cory L. Curtis
- (2001-06-23)

Related Posts:

• No Related Posts

It’s also time to remove the photo’s I think to a personal website and step this up to a more professional level. I’ve tried to get some more content writers involved but they never seem to take enough of an interest to add anything. Thanks to Jeff though, who although he’s not a computer tech, he’s added some funny items and a few solutions to some difficult problems.

As always, your feedback is welcome here.

- Cory L. Curtis
- (2011-06-19)

Related Posts:

• No Related Posts