Hi, 

Thanks for giving reply. I already checked the port config but here( EncryptStorefile= true). 

mainly my issue is when i was trying to download webpage from BAM portal i am getting file was not found error in POP UP box...

As I mentioned in BizTalk, there is no out-of-box property called EncryptStorefile in any of theartifacts (pipeline properties, component etc). This seems to be your custom property from your component and this not related to the error you see.

I assume you getting this error while trying to save a the BAM portal webpage with resultset of your search in BAM-view. Again as I said, BAM portal doesnt have option to export the result set, you got to get the screen shot (Print screen button in your keyboard) . When you try to download the webpage, youre getting this error, may be because BAM portal uses Active X component and in your browser (or in your computer), downloading a page with Activex control is not allowed.

when i was trying to getinboundmessage i am getting file not found alert in pop up box

in Biztalk server we are using BAM tracking when we trying to download file from BAM portal we are getting file not found...

Issue is occurring for both inbound and outbound decrypted messages in Prod and UAT environments for some abc application.

But original data is not having any special characters other than system acceptable values i.e. UTF-8 standard from Source system.

For all the decrypted files from BAM are containing special characters in some place and that is changing the original format of the file hence partner is not able to open in excel sheet.

Example : Source system sent value as AddressLineTwoDesc= (empty) but our decrypted source file is showing as per snap.

  For the corresponding target file is having special characters in multiple places but not for the above corresponding field mapping value.

 

So Encryption/Decryption might be causing the problem.

To validate above statement, made the port config change (EncryptStoreFile=false" ,actual value true ) in Decode stage at Receive location and Encode stage in send port in UAT.

Verified todays message after that, files from Downloadwebpage links are not having special characters. We are able to open out file in excel sheet.

We reverted back these changes now.

File Not Found & Special Character issue with some application views

• Edited by vasu sri Thursday, February 19, 2015 8:10 AM proper format
• Moved by Guillaume Rouyre [MBA, MVP, P-Seller]MVP Thursday, February 19, 2015 8:39 AM Wrong forum

Hello, you have posted your question in the Microsoft Project Customisation forum - please repost in the correct forum which relates to your question. 

this is in Biztalk server 

Guess what, I should have seen that in the title!  I'll let you re-post in the BizTalk forum.

Hi Vasu,

Your statements are contradictory and seem to more specific error pertaining to your custom components.

BAM tracking when we trying to download file from BAM portal we are getting file not found... out-of-box BAM portal does not have option to download the result as file. May be youre trying to do FileSave As option. If you trying to save the BAM portal web page as file and if you get this error, then its specific to your web browser used. Check web browser configuration.

validate above statement, made the port config change (EncryptStoreFile=false" ,actual value true ) in Decode stage at Receive location and Encode stage in send port No out-of-box decode/encode pipeline component has these properties. Seems like you have custom BizTalk component and the issue seems to be in your custom component.

Came back to us with clearer information about your issue and we can help. Your issues seems to be specific to your BizTalk (still not sure whether this issue is anything to do with BizTalk, other than the fact the question has some BizTalk terms) .

If you see any encryption issue in the messages transportation. Enable tracking in ports (or in Orchestration if you have one) check the message received, constructed at your end and one sent out.

You will want to ensure that if your pipeline that the message comes through has the Byte order mark (BOM) on or off.  Typically, UTF-8 one will default to it being on.  BAM does not like the BOM.  The special character is the BOM.