[smoothiegunner]

Hi everyone. I have a brandnew BESX install and the Attachment Server is not working. When trying to open an attachment on the device (BB Bold 9000) I receive error: "Cannot find attachment server". When testing using the Blackberry Server Configuration tool, I receive error: "An unspecified error occured during conversion process". Attachment Server is configured on same server as BESX. Server name is ORION and from the log files I could determine that the server listens on ORION. Telnet from the server on port 1900 1999 work. Errors in ASCL log files are: "Attachment Service not running or invalid configuration".

Any ideas? Thanks.

[smoothiegunner]

Come on, anyone? This is a really pressing issue.

[noname]

You see error is "Attachment Service not running or invalid configuration", what will you do?

[smoothiegunner]

Originally Posted by noname

You see error is "Attachment Service not running or invalid configuration", what will you do?

Based on your signature I presume that you have a better knowledge of what I might be checking thus the answer you gave is worthless.

Attachment Service IS running and as for a correct configuration (so I know what's wrong with mine) I have no idea where to look. I gave plenty of details regarding my troubleshooting. It's a clean install so it must be some stupid error. So, do you have some useful advice? What would you do in my situation? Give yourself the same answer?

[smoothiegunner]

I read also the installer log and in there I found: BAS was detected to have started, URL h ttp://orion:18180/
Yet on that specific page I have only HTTP Status 404 - / from JBoss

[smoothiegunner]

OK, finally solved it. Here is my solution:
Go to: C:\Program Files\Research In Motion\BlackBerry Enterprise Server\AttachServer. Ran BBAttachConfig.exe and change servername from localhost to ORION (in my case) (servername). Afterwards reboot server and bingo.

[knottyrope]

Thanks for sharing.

[nhoague]

Sorry to bump a very old thread ... but hopefully someone has an answer for this one!

We have just had to restore our BESMgmt.mdb due to server crash. Upon rebuilding the new server we renamed it to something more to our liking, we're calling it "BES101." The OLD server was just some random windows name, "WIN-QG6VZ2XN5OD."

Obviously with the change in hostname I knew I would have to make some adjustments. Not a big deal. Turned up new server, installed BES, setup SQL Management, restored our BESMgmt.mdb and then modified all the instances of WIN-QG6VZ2XN5OD to match BES101 in the db. Started BES services in order, and voila, all was good. All our blackberries started connecting and users are happy! Basically, a successful disaster recovery.

NOW, the problem is with the attachments. Users on their blackberries get the infamous "Attachment server not found" message. I toggled the BBAttachServer config between localhost and bes101. No luck. I checked the registry for the attach service, it is set to localhost. I tried toggling the service between Administrator and Local System, no luck. I can successfully check an attachment using the Test Attachment Server, and I can force an unsuccessful check when I use a fictitious server name. SO I know it is working.

Now, here is the kicker. After modifying pretty much EVERYTHING I can think of, my ASCL log file still shows this:

[10000] (11/25 06:43:35.637):{0x18C} [thr:0x018C] CArznSocket::Open() - gethostbyname(WIN-QG6VZ2XN5OD) failed with WSALastError 11004
[10000] (11/25 06:43:35.637):{0x18C} [thr:0x018C] CArznSocket::Close() - m_connectSocket = 0xFFFFFFFF, after
[10000] (11/25 06:43:35.637):{0x18C} [thr:0x018C] CArznFileConversionSubmit::Connect() - _OpenSocket() failed with hr=0x80004005
[10000] (11/25 06:43:35.637):{0x18C} [thr:0x018C] do_connect() of WIN-QG6VZ2XN5OD at index 0 failed with rc = 1016

Obviously the Attachment Service is still trying to pull the OLD server name from somewhere! Any thoughts where it is getting this? My thought was the database, but using a search string to check the entire database, this is no where to be found.

Your help is greatly appreciated.

[OliC]

Just registered to add to this. I had the exact same problem after moving the database from one server to another. After a lot of searching I eventually found the entry in the database where the attachment server was getting the old server name.

You need to open the table dbo.BASServiceInstanceData. I had 4 ServiceInstanceIDs here. The bottom two, numbered 18 and 19 on my server, contained 2 references each to the old server which I changed. It was quite hard to make the change 'stick' in SQL server but after it did and I restarted the services, the users could then open their attachments.

[jbfb99]

I ran into a very similar situation where the database did not reference the appropriate attachment server despite the BAS indicating everything was configured appropriately. I was able to update the database by editing the attachment server components in the BAS, removing all the connections under Supported Attachment Connector instances - save all - add them back - save all.