Re: Export-Mailbox issue
This happens in our environment. I have found that I have to uninstall KB2687623 more than once because it seems to re-appear after uninstalling a different Outlook update. Triple check that that didn't happen. I do really wish they would fix this! On 3/21/2013 3:43 PM, Miller Bonnie L. wrote: We have a yearly cleanup process that I'm running which involves exporting mailboxes to psts before deleting them. The specific command I use looks like: get-mailbox -OrganizationalUnit domain.name/ouname/InactiveAccounts | export-Mailbox -PSTFolderPath C:\PSTs -BadItemLimit 10 -ReportFile C:\-MM-DDExportReport.xml We now have Exchange 2007 SP3 RU10, and I run it from a 32 bit machine with Outlook installed as an admin that has full access to the mailboxes. This year, I've updated my tools machine to Win7 (was XP), and I'm getting a crash in powershell when trying to run the export. Digging around in the logs, I find the specific error displayed is: Error was found for User (usern...@domain.name) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219 After more digging online and checking all sorts of permissions and elevation (not the issue), I ran across this thread, indicating issues after some updates to Office 2010. I tried uninstalling just the updates mentioned, but only found two of the three and did not have any luck with it working. Because it's a pretty basic installation (and not my main machine that I use), I removed Office 2010 and reinstalled with no fixes, at which point the command runs without crashing. http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/1a979543-c4f8-4504-8870-95612c81b181 So, has anyone run into this and/or know if it's in the works to be fixed? I'm also really looking for the SPECIFIC update causing the problem, as it would be nice to patch it up and just roll off the problem one when I need export-mailbox. For now I'm just going to leave the machine off until I can run the full export of all the mailboxes on Monday, so it doesn't re-patch itself, or figure out how to get infected. I guess it will all change again soon when we get to 2013 anyway... Thanks, Bonnie --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com mailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
Re: List members sending OOF replies
Good luck with that. You'd probably be much better served by creating a rule that just sent OOF messages to trash. In my ~12 years on the sunbelt lists you aren't the first person to make such an observation or request. On Fri, Mar 22, 2013 at 8:54 AM, Dean d...@ripperd.com wrote: It seems we have a number of Admins who send OOF replies to list posters. I received 19 Out of Office messages when I posted to the list last night. Admins, please fix your Out of Office rules to not respond to list-only posts. --- To manage subscriptions click here: http://lyris.sunbelt-software.** com/read/my_forums/ http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmanager@lyris.**sunbeltsoftware.comlistmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Export-Mailbox issue
I didn't see it on the list, but now that you mention that, it makes me think there could also be some patch supercedence going on here, as we are all up-to-date through now. I'll have to look at our WSUS server on Monday (I'm off today) and look for a chain--there could be another patch number involved that I'm not catching. Thanks! Bonnie From: Dean E [d...@ripperd.com] Sent: Thursday, March 21, 2013 11:51 PM To: MS-Exchange Admin Issues Subject: Re: Export-Mailbox issue This happens in our environment. I have found that I have to uninstall KB2687623 more than once because it seems to re-appear after uninstalling a different Outlook update. Triple check that that didn't happen. I do really wish they would fix this! On 3/21/2013 3:43 PM, Miller Bonnie L. wrote: We have a yearly cleanup process that I’m running which involves exporting mailboxes to psts before deleting them. The specific command I use looks like: get-mailbox -OrganizationalUnit domain.name/ouname/InactiveAccounts | export-Mailbox -PSTFolderPath C:\PSTs -BadItemLimit 10 -ReportFile C:\-MM-DDExportReport.xml We now have Exchange 2007 SP3 RU10, and I run it from a 32 bit machine with Outlook installed as an admin that has full access to the mailboxes. This year, I’ve updated my tools machine to Win7 (was XP), and I’m getting a crash in powershell when trying to run the export. Digging around in the logs, I find the specific error displayed is: Error was found for User (usern...@domain.namemailto:usern...@domain.name) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219 After more digging online and checking all sorts of permissions and elevation (not the issue), I ran across this thread, indicating issues after some updates to Office 2010. I tried uninstalling just the updates mentioned, but only found two of the three and did not have any luck with it working. Because it’s a pretty basic installation (and not my main machine that I use), I removed Office 2010 and reinstalled with no fixes, at which point the command runs without crashing. http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/1a979543-c4f8-4504-8870-95612c81b181 So, has anyone run into this and/or know if it’s in the works to be fixed? I’m also really looking for the SPECIFIC update causing the problem, as it would be nice to patch it up and just roll off the problem one when I need export-mailbox. For now I’m just going to leave the machine off until I can run the full export of all the mailboxes on Monday, so it doesn’t re-patch itself, or figure out how to get infected. I guess it will all change again soon when we get to 2013 anyway… Thanks, Bonnie --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Export-Mailbox issue
You have days off? What's that like? From: Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu] Sent: Friday, March 22, 2013 7:29 AM To: Heaton, Joseph@Wildlife; MS-Exchange Admin Issues Subject: RE: Export-Mailbox issue I didn't see it on the list, but now that you mention that, it makes me think there could also be some patch supercedence going on here, as we are all up-to-date through now. I'll have to look at our WSUS server on Monday (I'm off today) and look for a chain--there could be another patch number involved that I'm not catching. Thanks! Bonnie From: Dean E [d...@ripperd.com] Sent: Thursday, March 21, 2013 11:51 PM To: MS-Exchange Admin Issues Subject: Re: Export-Mailbox issue This happens in our environment. I have found that I have to uninstall KB2687623 more than once because it seems to re-appear after uninstalling a different Outlook update. Triple check that that didn't happen. I do really wish they would fix this! On 3/21/2013 3:43 PM, Miller Bonnie L. wrote: We have a yearly cleanup process that I'm running which involves exporting mailboxes to psts before deleting them. The specific command I use looks like: get-mailbox -OrganizationalUnit domain.name/ouname/InactiveAccounts | export-Mailbox -PSTFolderPath C:\PSTs -BadItemLimit 10 -ReportFile C:\-MM-DDExportReport.xml We now have Exchange 2007 SP3 RU10, and I run it from a 32 bit machine with Outlook installed as an admin that has full access to the mailboxes. This year, I've updated my tools machine to Win7 (was XP), and I'm getting a crash in powershell when trying to run the export. Digging around in the logs, I find the specific error displayed is: Error was found for User (usern...@domain.namemailto:usern...@domain.name) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219 After more digging online and checking all sorts of permissions and elevation (not the issue), I ran across this thread, indicating issues after some updates to Office 2010. I tried uninstalling just the updates mentioned, but only found two of the three and did not have any luck with it working. Because it's a pretty basic installation (and not my main machine that I use), I removed Office 2010 and reinstalled with no fixes, at which point the command runs without crashing. http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/1a979543-c4f8-4504-8870-95612c81b181 So, has anyone run into this and/or know if it's in the works to be fixed? I'm also really looking for the SPECIFIC update causing the problem, as it would be nice to patch it up and just roll off the problem one when I need export-mailbox. For now I'm just going to leave the machine off until I can run the full export of all the mailboxes on Monday, so it doesn't re-patch itself, or figure out how to get infected. I guess it will all change again soon when we get to 2013 anyway... Thanks, Bonnie --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Export-Mailbox issue
LOL, and I'm checking my work e-mail still, so does it really count? Nice and snowy today here in the WA mountains =) From: Heaton, Joseph@Wildlife [joseph.hea...@wildlife.ca.gov] Sent: Friday, March 22, 2013 8:00 AM To: MS-Exchange Admin Issues Subject: RE: Export-Mailbox issue You have days off? What’s that like? From: Miller Bonnie L. [mailto:mille...@mukilteo.wednet.edu] Sent: Friday, March 22, 2013 7:29 AM To: Heaton, Joseph@Wildlife; MS-Exchange Admin Issues Subject: RE: Export-Mailbox issue I didn't see it on the list, but now that you mention that, it makes me think there could also be some patch supercedence going on here, as we are all up-to-date through now. I'll have to look at our WSUS server on Monday (I'm off today) and look for a chain--there could be another patch number involved that I'm not catching. Thanks! Bonnie From: Dean E [d...@ripperd.com] Sent: Thursday, March 21, 2013 11:51 PM To: MS-Exchange Admin Issues Subject: Re: Export-Mailbox issue This happens in our environment. I have found that I have to uninstall KB2687623 more than once because it seems to re-appear after uninstalling a different Outlook update. Triple check that that didn't happen. I do really wish they would fix this! On 3/21/2013 3:43 PM, Miller Bonnie L. wrote: We have a yearly cleanup process that I’m running which involves exporting mailboxes to psts before deleting them. The specific command I use looks like: get-mailbox -OrganizationalUnit domain.name/ouname/InactiveAccounts | export-Mailbox -PSTFolderPath C:\PSTs -BadItemLimit 10 -ReportFile C:\-MM-DDExportReport.xml We now have Exchange 2007 SP3 RU10, and I run it from a 32 bit machine with Outlook installed as an admin that has full access to the mailboxes. This year, I’ve updated my tools machine to Win7 (was XP), and I’m getting a crash in powershell when trying to run the export. Digging around in the logs, I find the specific error displayed is: Error was found for User (usern...@domain.namemailto:usern...@domain.name) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219 After more digging online and checking all sorts of permissions and elevation (not the issue), I ran across this thread, indicating issues after some updates to Office 2010. I tried uninstalling just the updates mentioned, but only found two of the three and did not have any luck with it working. Because it’s a pretty basic installation (and not my main machine that I use), I removed Office 2010 and reinstalled with no fixes, at which point the command runs without crashing. http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/1a979543-c4f8-4504-8870-95612c81b181 So, has anyone run into this and/or know if it’s in the works to be fixed? I’m also really looking for the SPECIFIC update causing the problem, as it would be nice to patch it up and just roll off the problem one when I need export-mailbox. For now I’m just going to leave the machine off until I can run the full export of all the mailboxes on Monday, so it doesn’t re-patch itself, or figure out how to get infected. I guess it will all change again soon when we get to 2013 anyway… Thanks, Bonnie --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.commailto:listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
RE: Off Topic Remote Exchange Powershell Issues.
Can't say for sure, but this part looks suspicious: System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.Exchange.Data.Storage.ExchangePrincipal.get_ServerFullyQualifiedDomainName() at Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(MapiStore linkedStore, LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, GenericIdentity auxiliaryIdentity) One notable difference between running the script yourself and running it from a scheduled task is the logon type (interactive vs. batch). From: Pfefferkorn, Pete (pfeffepe) [mailto:pfeff...@ucmail.uc.edu] Sent: Friday, March 22, 2013 12:17 PM To: MS-Exchange Admin Issues Subject: Off Topic Remote Exchange Powershell Issues. This is a little off topic but I've been banging my head against a wall trying to figure it out. We have Exchange 2010 SP2. We have a virtual machine which we setup that runs all our scripts against Exchangeprovisioning, de-provisioning, reporting monitoring etc. I have dozens of scripts running on that box that run fine except for a couple that just won't run correctly in the task scheduler. If I run them adhoc on that box...not a problem. The scheduler doesn't report any errors either but I don't get results. Simple test is as follows: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 $error.clear() get-InboxRule -mailbox xx | export-csv pete.csv get-mailbox xx | export-csv pete2.csv The get-mailbox works fine when it runs from the scheduled task. The get-inboxRule nada. Blank file. Task is set to run with highest priv. Powershell versions match. If I run this on one of our Exchange servers as a scheduled task...not a problem. I can put these couple of scripts on one of the servers but I would rather figure out the problem and get them back on our management box. In the Event Viewer I see under Windows PowerShell events 403, 400, and 600 For Engine and Provider Lifecycle. In the Exchange event I see two events recorded and event ID 6 and Event ID 8. I'm thinking it's a piping issue but I would think it would fail in both circumstances ad-hoc and as a task. Log Name: MSExchange Management Source:MSExchange CmdletLogs Date: 3/22/2013 1:09:38 PM Event ID: 8 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: UCMAILMGR.ad.uc.edu Description: The description for Event ID 8 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Log Name: MSExchange Management Source:MSExchange CmdletLogs Date: 3/22/2013 1:09:38 PM Event ID: 8 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: UCMAILMGR.ad.uc.edu Description: The description for Event ID 8 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 1620 5 Get-InboxRule Get-InboxRule System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.Exchange.Data.Storage.ExchangePrincipal.get_ServerFullyQualifiedDomainName() at Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(MapiStore linkedStore, LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, GenericIdentity auxiliaryIdentity) at Microsoft.Exchange.Data.Storage.MailboxSession.c__DisplayClass12.CreateMailboxSessionb__10(MailboxSession mailboxSession) at Microsoft.Exchange.Data.Storage.MailboxSession.InternalCreateMailboxSession(LogonType logonType, ExchangePrincipal owner, CultureInfo cultureInfo, String clientInfoString, IAccountingObject budget, Action`1 initializeMailboxSession, InitializeMailboxSessionFailure initializeMailboxSessionFailure) at Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString, PropertyDefinition[] mailboxProperties, IList`1 foldersToInit, GenericIdentity auxiliaryIdentity, IAccountingObject budget) at
RE: Off Topic Remote Exchange Powershell Issues.
I think I reported this during the E15 TAP but there was no backport. Try this: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 $error.clear() $mb = get-mailbox xx $mb | get-InboxRule | export-csv pete.csv $mb | export-csv pete2.csv The problem is that get-InboxRule can't figure out what server it is supposed to be talking to and it doesn't take a -Server parameter. From: Pfefferkorn, Pete (pfeffepe) [mailto:pfeff...@ucmail.uc.edu] Sent: Friday, March 22, 2013 1:17 PM To: MS-Exchange Admin Issues Subject: Off Topic Remote Exchange Powershell Issues. This is a little off topic but I've been banging my head against a wall trying to figure it out. We have Exchange 2010 SP2. We have a virtual machine which we setup that runs all our scripts against Exchangeprovisioning, de-provisioning, reporting monitoring etc. I have dozens of scripts running on that box that run fine except for a couple that just won't run correctly in the task scheduler. If I run them adhoc on that box...not a problem. The scheduler doesn't report any errors either but I don't get results. Simple test is as follows: Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 $error.clear() get-InboxRule -mailbox xx | export-csv pete.csv get-mailbox xx | export-csv pete2.csv The get-mailbox works fine when it runs from the scheduled task. The get-inboxRule nada. Blank file. Task is set to run with highest priv. Powershell versions match. If I run this on one of our Exchange servers as a scheduled task...not a problem. I can put these couple of scripts on one of the servers but I would rather figure out the problem and get them back on our management box. In the Event Viewer I see under Windows PowerShell events 403, 400, and 600 For Engine and Provider Lifecycle. In the Exchange event I see two events recorded and event ID 6 and Event ID 8. I'm thinking it's a piping issue but I would think it would fail in both circumstances ad-hoc and as a task. Log Name: MSExchange Management Source:MSExchange CmdletLogs Date: 3/22/2013 1:09:38 PM Event ID: 8 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: UCMAILMGR.ad.uc.edu Description: The description for Event ID 8 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Log Name: MSExchange Management Source:MSExchange CmdletLogs Date: 3/22/2013 1:09:38 PM Event ID: 8 Task Category: (1) Level: Error Keywords: Classic User: N/A Computer: UCMAILMGR.ad.uc.edu Description: The description for Event ID 8 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: 1620 5 Get-InboxRule Get-InboxRule System.InvalidOperationException: Operation is not valid due to the current state of the object. at Microsoft.Exchange.Data.Storage.ExchangePrincipal.get_ServerFullyQualifiedDomainName() at Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(MapiStore linkedStore, LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, GenericIdentity auxiliaryIdentity) at Microsoft.Exchange.Data.Storage.MailboxSession.c__DisplayClass12.CreateMailboxSessionb__10(MailboxSession mailboxSession) at Microsoft.Exchange.Data.Storage.MailboxSession.InternalCreateMailboxSession(LogonType logonType, ExchangePrincipal owner, CultureInfo cultureInfo, String clientInfoString, IAccountingObject budget, Action`1 initializeMailboxSession, InitializeMailboxSessionFailure initializeMailboxSessionFailure) at Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString, PropertyDefinition[] mailboxProperties, IList`1 foldersToInit, GenericIdentity auxiliaryIdentity, IAccountingObject budget) at Microsoft.Exchange.Data.Storage.MailboxSession.ConfigurableOpen(ExchangePrincipal mailbox, MailboxAccessInfo accessInfo, CultureInfo cultureInfo, String clientInfoString, LogonType logonType, PropertyDefinition[] mailboxProperties, InitializationFlags initFlags, IList`1 foldersToInit, IAccountingObject budget)
