Monday, May 30, 2011

V-79-57344-65298 - The Exchange Store service is not responding. Backup set canceled.


Problem


When the "Media Insert" alert is responded with CANCEL during the backup of a resource, the resource is not listed under the restore selection till the Backup Exec services are restarted

Solution


The above can be better explained with this example. Lets consider a Backup Job backing up C,D and E Drive of the local Server. After backing up the C and D drive when Backup Exec is backing up the E drive if the storage media is full and asking for a overwritable media and it is at this stage if the Backup Job is canceled we would only see the C and D in the Restore Job properties. The E drive which was partially backed up will not be seen until the Backup Exec services are restarted.

WORKAROUND:

Restart all Backup Exec Services to see the resource on which the request for overwritable media was canceled during the Backup operation.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or Hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see    http://www.symantec.com/ . Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

Friday, May 20, 2011

Outlook tracking tab shows attendees as optional when initial invite was sent to alias


This is issue is seen in the following scenario:
Outlook 2007 users with mailbox in exchange 2003 or 2007
User proposes a  meeting and has as only attendee an alias. After members of the alias accept the meeting, the meeting tracking tab shows those attendees as optional attendees.

Outlook meeting requests: Essential do’s and don’ts
http://office.microsoft.com/en-us/help/HA011276781033.aspx

It is not recommended practices to send meeting request to a Distribution Group. If you need to invite all the members of a distribution list, expand the list in the To line before sending the request.

Tuesday, May 17, 2011

Exchange 2010: Mailbox Auto reply configuration


Method 1 = Exchange Management Shell

Among all new cmdlets included with Exchange 2010, there are two very interesting ones in this context, namely:
Get and  Set-MailboxAutoReplyConfiguration
Looking at our demo mailbox, belonging to me, it’s clear there is no Out-Of-Office  configured yet:
SNAG-0107
When using the cmdlet Get-MailboxAutoReplyConfiguration, we retrieve the same information:
SNAG-0108
Using a single line in the shell, it’s rather easy to provision the mailbox with an Out-Of-Office:
Set-MailboxAutoReplyConfiguration –Identity ExternalAudience   -ExternalMessage –InternalMessage –AutoReplyState <disabled, enabled, or scheduled if you want to schedule the OOF to start at a defined StartTime and possibly end after defined EndTime>
 SNAG-0112
and this is how it looks using Outlook
 SNAG-0113

Method 2 = Using Exchange Control Panel

Using any browser I can log into the Exchange Control Panel:
image
Choose to manage Another User, like Ilse Van Criekinge, and configure on her behalf her Out Of Office
image
To finish, and save the settings, click Save








SNAG-0118

Wednesday, May 11, 2011

TNS-12537 TNS:connection closed

Solution:
I tried this solution from the Oracle forum:

This may be a route problem if the database is not on your local network.
Try "route add "
This solved my 12537 it hadn't even occurred to me that it was so simple.
End of file on communication channel when connecting meant can't find it not a database disconnection.