
但是我確定你輸入的帳號密碼是正確的,因為在ODBC使用原來的帳號密碼時,是可以登入成功的.
後來透過Google搜尋了一下,才知道這個地方輸入的帳號密碼大小寫是有分別的,後來將帳號全部改成大寫後,果然就真的過了,真是虛驚一場.
推薦這個部落格: 0


· For SQL Server 2008, run setup and choose the Management Tools: Basic and Management Tools: Complete options.
· For SQL Server 2005, run setup and chose the Management Tools option under SQL Server 2005 Client Tools.
1. Validate Map取得Xsl檔案

2. 用文字編輯器開啟xsl檔案,移除裡面ns0的字眼,若想連root節點namespace的ns0都移除的話也可以.
3.建立一新Map,此Map的Source與Destination都與原始一模一樣,但是不需要拉線.設定此map的Custom XSL Path屬性,指向上一步驟所修改過的XSL檔案.
4. 再次Test Map即可得到完全不含ns0的XML.
原來含有ns0的輸出XML.
目前BizTalk 2006 R2的AS2功能尚未支援自動重送的功能,也就是說,當你透過AS2正確的送出檔案後,若沒有收到正確的MDN時,BizTalk 2006 R2不會自動幫你重送該筆資料,這個功能需要到BizTalk 2009才會加入,底下是摘錄自BizTalk Server 2009 - EDI Product Team Blog.的新功能說明.
http://blogs.msdn.com/biztalkb2b/archive/2009/02/19/what-is-new-for-edi-as2-in-biztalk-2009.aspx
what is new for EDI/AS2 in BizTalk 2009Below is excerpts from BizTalk 2009 documentation about new features in BizTalk EDI /AS2 (BizTalk 2009): Electronic Data Interchange (EDI) is one of the most prevalent means by which businesses exchange data electronically. It represents approximately 75 percent of all business-to-business electronic transactions and grows at about 5 to 7 percent per year. EDI usage entails message syntax and standards (including ANSI X12 and UN/EDIFACT), messaging protocols, and transports. BizTalk Server 2006 R2 introduced the ability to process EDI messages using EDI pipeline components, as well as AS2 support. BizTalk Server 2009 improves EDI support with the following features: Dynamic EDI Envelope Generation: · Override EDI envelope settings at runtime by setting context properties. · Values configured in party resolution are used unless the specific value is overridden. Multiple Batches · Multiple batch configurations can be created for each party. · Batch lifecycle can be managed individually. HIPAA · HIPAA schemas now support equivalent segments. Transmitting EDI transactions over the Internet is an increasingly popular alternative to sending and receiving EDI using value-added networks (VANs). Using the Internet for data exchange reduces costs, increases efficiency, and has advantages in terms of redundancy and scalability. To support this growing trend, BizTalk Server 2006 R2 introduced support for EDIINT AS/2 (Applicability Statement 2). AS/2 is a specification that enables transport of business data over the Internet in a safe and reliable manner. BizTalk Server uses AS/2-defined methods to send, receive, encrypt, decrypt, decompress, sign, and verify signatures between partners using HTTP over the Internet. BizTalk Server helps ensure the security of messages through the use of encryption keys, digital signatures, certificates, and non-repudiation. BizTalk Server 2009 introduces the following AS/2 features: · Drummond Group certified for multi-file attachment support, file name preservation support and interoperability. · Resend messages if an MDN has not been received within a specified time frame. · Send and receive multiple file attachments. · Preserve attachment file names. |
| Certificate Usage | Certificate Type | Pipeline Component | User Context | Certificate Store | Where Defined |
|---|---|---|---|---|---|
Signature (outbound) | Own private key (.pfx) | MIME/SMIME encoder | Account used by the host instance associated with the send handler. | Current User\ | Certificate page of the Group Properties dialog box |
Signature verification (inbound) | Trading partner's public key (.cer) | MIME/SMIME decoder | Account used by the host instance associated with the receive handler. | Local computer\Other People store of each BizTalk server that hosts a MIME/SMIME decoder pipeline as each host instance service account | Certificate page of the Party Properties dialog box Note: The certificate used to verify a signature for a party must be unique from the certificates used to verify signatures for other parties. |
Encryption (outbound) | Trading partner's public key (.cer) | MIME/SMIME encoder | Account used by the host instance associated with the send handler. | Local computer\Other People store of each BizTalk server that hosts a MIME/SMIME encoder pipeline | Certificate page of the Send Port Properties dialog box |
Decryption (inbound) | Own private key (.pfx) | MIME/SMIME decoder | Account used by the host instance associated with the receive handler. | Current User\Personal store of each BizTalk server that hosts a MIME/SMIME decoder pipeline as each host instance service account | The AS2 Decoder will determine the certificate based upon certificate information in the message. For the BizTalk MIME Decoder, the certificate must be in the Certificate page of the host used for receiving the message. This is not necessary for the AS2 Decoder. |


| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 |