[wunderbar]

Okay, I've been looking at this all morning, and I'm not sure what's going on. I had disabled my device's ability to view PDF's until I was able to apply the most recent patch for the PDF vulnerability, but now my devices cannot view PDF files, even after I've enabled them.

In the blackberry server configuration I have made sure that pdf is in the list for allowed format extensions, it is also turned on in the distiller in the attachment server configuration, and i have restarted the attachment service. I even did a battery pull on my device to see if that might be it. I can confirm that other attachment types are working. I was able to view both a .doc and a .docx.

Anyone?

EDIT: also, information on my signature is accurate, except that it's at 4.1.6 MR3 with the latest PDF distiller patch.

[DarthBBerry]

Restart attachment service and dispatcher?

[wunderbar]

Yes, I just double checked that by restarting them both. Problem still exists.

[DarthBBerry]

How about adding the file extention back in under the Connector Configuration for the Attachment Server tab? There's 2 places ya know....
Connector Configuration and Attachment Server; both are drop down menus.

[wunderbar]

Originally Posted by DarthBBerry

How about adding the file extention back in under the Connector Configuration for the Attachment Server tab? There's 2 places ya know....
Connector Configuration and Attachment Server; both are drop down menus.

yea, it's in both those locations too.

That's what I don't get, it looks right, I documented the changes I made before hand, and reversed the changes. The only thing I have left to try is to roll back the patch, and see if that possibly caused the problem.

[DarthBBerry]

Only other thing I can think of is to re-register the PDF patch DLL files.

[wunderbar]

Done that. Didn't work.

Time to roll back the patch I guess and see if it even worked in the state it was in before hand. we only have 35 users, and very few of them use it to it's fullest potential. It could have gone on for weeks un-noticed if I hadn't tried opening a PDF.

[DarthBBerry]

Now you have me concerned about applying the PDF - DLL patch. Thanks, man!

[wunderbar]

Well I rolled the patch back to the previous version of the DLL's, and the problem still exists, so it's likely something else.

gonna check a few more things, then it might just be time for a TSupport call.

[DarthBBerry]

Originally Posted by wunderbar

Well I rolled the patch back to the previous version of the DLL's, and the problem still exists, so it's likely something else.

gonna check a few more things, then it might just be time for a TSupport call.

While you're on with T-Support, ask them about my duplicate Messages[Desktop] issue. See Duplicate Settings in Profile thread.

[stuwhite]

Originally Posted by DarthBBerry

Now you have me concerned about applying the PDF - DLL patch. Thanks, man!

I did this last week Darth and all was fine. It's literally just replacing 3 DLLs so if it all goes wrong, no biggie to get back. I went straight to MR3 and the PDF "patch" at the same time and all has been good.

[Jadey]

Originally Posted by DarthBBerry

While you're on with T-Support, ask them about my duplicate Messages[Desktop] issue. See Duplicate Settings in Profile thread.

Well, if we're playing that game, can you ask them about my BBM issues too? http://www.blackberryforums.com/gene...-contacts.html

[DarthBBerry]

Originally Posted by Jadey

Well, if we're playing that game, can you ask them about my BBM issues too? http://www.blackberryforums.com/gene...-contacts.html

Commented on your post. I feel your pain.

[TreeDude]

Ever figure this out wunderbar? Just applied MR4 last night and I now have the same issue.

[TreeDude]

Never mind. A reboot after turning them back on did the trick.

[noname]

Yeah I do not trust regsrv32 anymore. E.g. my SMS for Domino cannot be started due to a DLL failure, did so many regsitering until I gave up and recycled the OS. I think its a Windows problem here too.