Discussion:
CRM 4 error 'must be a forward-as-attachment' creating .bin files instead
(too old to reply)
Mous
2010-07-09 16:19:42 UTC
Permalink
For the past two or so weeks, the forward mailbox is receiving all
messages with an att00001.bin attachment instead of the usual <name of
subject line>.msg attachment. This is causing the mailbox to fill up
and move to the undeliverable folder. I have done a lot of things to
try and fix this but nothing has worked (with the exception of not
using the forward mailbox, then things get delivered correctly but
this is not a viable solution). I have done the following:

Double checked that the rule is indeed forwarding as an attachment.
Uninstalled crm email router/reinstalled (kept all settings)
Created another forward mailbox (same issue)
Manually created a rule on my pc's outlook and forwarded two messages
at once which creates an attachment to someone which still showed up
as a .bin.
Switched to text only in outlook
Restarted mail and crm servers
Uninstalled software updates after a certain date
Uninstalled crm client for outlook on my pc and reinstalled
Removed the rules by starting w/ the removeserverrule switch for
admin, myself, forward mailbox then pushed out again.
Removed the rule from everyone and pushed out to me only to test (it
does push out ok and does move to forward mailbox but still w/
the .bin extension)
Ran the diag tool but that doesn't seem to show me anything
significant that I can see

The weird thing is, a few emails get tracked under history (know this
by running a report on current date emails in history). It's not
EVERY email for those users, just a few so it's hard to pinpoint why
those are going through but the majority are not.

Using exchange 07 and no errors in event log on that server. the only
ones I'm getting in crm are the forward as attachment ones and a
crmsql that says the Configuration option 'show advanced options'
changed from 1 to 0. Run the RECONFIGURE statement to install. Then a
second one after it saying it changed from 0 to 1. These are coming
up a LOT more lately.

I'm pulling my hair out...has anyone had experience with this?
Thank you.
Mous
2010-07-19 17:24:00 UTC
Permalink
Post by Mous
For the past two or so weeks, the forward mailbox is receiving all
messages with an att00001.bin attachment instead of the usual <name of
subject line>.msg attachment.  This is causing the mailbox to fill up
and move to the undeliverable folder.  I have done a lot of things to
try and fix this but nothing has worked (with the exception of not
using the forward mailbox, then things get delivered correctly but
Double checked that the rule is indeed forwarding as an attachment.
Uninstalled crm email router/reinstalled (kept all settings)
Created another forward mailbox (same issue)
Manually created a rule on my pc's outlook and forwarded two messages
at once which creates an attachment to someone which still showed up
as a .bin.
Switched to text only in outlook
Restarted mail and crm servers
Uninstalled software updates after a certain date
Uninstalled crm client for outlook on my pc and reinstalled
Removed the rules by starting w/ the removeserverrule switch for
admin, myself, forward mailbox then pushed out again.
Removed the rule from everyone and pushed out to me only to test (it
does push out ok and does move to forward mailbox but still w/
the .bin extension)
Ran the diag tool but that doesn't seem to show me anything
significant that I can see
The weird thing is, a few emails get tracked under history (know this
by running a report on current date emails in history).  It's not
EVERY email for those users, just a few so it's hard to pinpoint why
those are going through but the majority are not.
Using exchange 07 and no errors in event log on that server.  the only
ones I'm getting in crm are the forward as attachment ones and a
crmsql that says the Configuration option 'show advanced options'
changed from 1 to 0. Run the RECONFIGURE statement to install. Then a
second one after it saying it changed from 0 to 1.  These are coming
up a LOT more lately.
I'm pulling my hair out...has anyone had experience with this?
Thank you.
For anyone who happens to run across this same issue, it was the
upgrade to Policy Patrol 7 that caused it. Ended up having to keep v.
7 but changed on exchange to make a journaling entry under org hub
transport to get around this.

Loading...