Solved

Blackberry Unrecognized document format .doc

Posted on 2012-03-28
4
1,053 Views
Last Modified: 2012-04-02
Hi
I am getting the same problem with a bold 9700, 9900 and a torch 9800
all run on the same BIS ver 4.1.4.17 server, Exchange 2003.

Sent a .doc attachment to device, try to open it says:
X unrecognized document format.

used ms word to change the font in the document from century gothic to arial.
sent it back to the device, now I can open the attachment without problem.

Is there some font that are not compatible with my device?

What can I do to fix this since you cannot ask all your contact to only send
some type of font in their documents.


Thanks
0
Comment
Question by:celyn1
  • 2
  • 2
4 Comments
 
LVL 32

Accepted Solution

by:
Rodney Barnhardt earned 500 total points
ID: 37786848
If this post twice, sorry I hit submit the first time and it doesn't seem to have uploaded. I am not as familiar with BIS as BES, but this version seems to be a few years old. We ran into a problem several years ago where once we moved to Office 2007 this was big problem. It had to do with BES 4.1 versions not being compatible with the newer versions of Office. This was mostly corrected with MP6 and 7. There was still a know issue, for which there is a KB, that if the document was created in a version earlier than 2007, but then edited in 2007 or 2010, the "unrecognized document format" error would still occur. We mainly saw this on older templates we used to send out annoucments. I am not sure there was a plan to correct this in a 4.1 version since 5.0 has been out for a while. I migrated my users last year and am not aware of this problem happening since. There could also be an issue with the attachment service since that is supposed to format documents to be read, you could check it, but once again it may be a version issue.
0
 

Author Comment

by:celyn1
ID: 37796563
Hi  rbarnhardt,
thank you for sharing your experience with this similar issue, I taught as much that my BIS 4 could be the problem... But since in my case it's a font problem and not a Word file type compatibility issue, (changing font in the document fix the error), I was hoping I was just missing some quick fix.

The not so friendly migration from BIS4 to BES5 annoys me. But I guest it's time to get up to date if I want to be working without those kind of error and annoyance that might arise in a near future with my outdated system.
0
 
LVL 32

Expert Comment

by:Rodney Barnhardt
ID: 37796602
I didn't find it that big of a pain. I stood up a new upgraded environment and used the Enterprise Transporter to migrate the users to the new system. Worked pretty seemlessly. The largest amount of time was in getting the new environment set up because I went to a new Windows 2008 RS server for BES and a seperate Windows 2008 R2 w/SQL 2008 system for the database. I have about 130 users.
0
 

Author Comment

by:celyn1
ID: 37796900
Thanks for the info
In my case the problem with the migration is that we do not have a spare server to install BES5 and we can only run BES 4.1 and BES Express in the same Domain on separate servers.

So I have to de-install 4.1, install 5 then a wipe of the device to activate on BES Express 5.0, until this is done and fully operational all the blackberries will turn into simple dumb telephone .. I will get kill that's for sure.
-----------
Edit: found on a forum :  I do not have to wipe my devices.  I just have to delete my Desktop service books, and do a battery pull and I'm ready to re-activate. No need to wipe the device though. Interesting.
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now