One work around for Management Portal Issues. ESB 2.1 Part 2 – Missing Application

Errors:
 
 I have yet to find the reason why esb.exception handling doesn’t get added when the rest do.
(This happens when you choose SSO and apply the Configuration selection in the ESB Configuration Toolkit. )
 
The "work around" has been to remove it from SSO and use a "File Configuration like so"
 
 THe rest
 
 
 

This below not fix the SSODB problem, it does however fix the error from arising when trying to navigate to the portal home page.

SSO AUDIT

Function: GetConfigInfo (SSOProperties)
Tracking ID: 97fbc4ce-9a27-4f1c-bd9c-73953cd96f8a
Client Computer: IRDEV (w3wp.exe:3976)
Client User: IRDEVAdministrator
Application Name: ESB.exceptionHandling
Error Code: 0xC0002A04, The application does not exist.
 

This led me to think  ESB.exceptionHandling belongs in the SSO DB.
 
 
Actually the above was just another error that triggered an exception which caused the SSO to get hit for the esb.exceptionHandling application, and it wasn’t listed in the SSODB .
 
 
 
I even just tried adding ESB.exceptionHandling and adding the row to the DB manually.  After I received an Incorrect Parameter error.  
 
 
 
 
I created a dual boot machine ot throw 2.0 back up to see if it was added during 2.0 and it isn’t.
 
 
 
 
I had originally created individual web sites for ESB Web Exception and Core Web Services. Originially these had bindings that weren’t the same as the default website.
 
 
After removing those two Websites, I went back into the configuration tool and reset the Website Names to default website for both Angel
This was due to the fact that each site had it’s own Bindings and the sites were expecting these to be in the same binding set.  I still need to research if this is due to relative path calls (so they would have to be on the same bindings) or some configuration file that is used reference the call, that can be changed.
 
 
The resulting website looked like so:
 
 
After the esb portal  came up fine.
 
 

Share on Facebook

Management_Install.cmd work around.

Keywords:
BizTalk 2010 Beta
ESB 2.1
Management_Install.ps1
 
 
You more than likely kept the ESBSource directory when copying over.
Copy Keys and Source directly into:
 C:ProjectsMicrosoft.Practices.ESB
 
 
You sill still get the red flashes in your command window.
You will need to open up the Management_install.ps1 and change
$env:VS="${env:ProgramFiles}Microsoft Visual Studio 10.0Common7IDE"
to
$env:VS="C:Program Files (x86)Microsoft Visual Studio 10.0Common7IDE"  ifyou are using a 64 bit machine)
 
It worked fine afterwords.
 
 
Share on Facebook

Holder for Biztalk Install – ESB

 

C:WindowsMicrosoft.NETFrameworkv4.0Windows Communication Foundation>ServiceModelReg.exe -r -y

I found it here:

C:WindowsMicrosoft.NETFramework64v4.0.30319

 

 

Server x64

cdProgram Files (x86)Microsoft BizTalk Server 2010Tracking
Bm.exe deploy-all -DefinitionFile:"C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.1BamMicrosoft.BizTalk.ESB.BAM.Exceptions.xml"
Bm.exe deploy-all -DefinitionFile:"C:Program Files (x86)Microsoft BizTalk ESB Toolkit 2.1BamMicrosoft.BizTalk.ESB.BAM.Itinerary.xml"

 

 

 

If you find :

           No connection could be made because the target machine actively refused it 127.0.0.1:2383

Start SQL Server Analysis Services (MSSQLSERVER).

Share on Facebook

Holder for Biztalk Install – 2 UDDI, Supporting Programs

Share on Facebook

Holder for Biztalk Install – 1

 
cscript %SYSTEMDRIVE%inetpubadminscriptsadsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
 
CdUsersAdministratorAppDataLocalTempPlatformSSOFiles
ssomanage -serverall IRDEV  <– sets for all users
ssomanage -server IRDEV   <– sets for this user
 
Share on Facebook

Starting from Scratch on EDIGUIDANCE Box

Windows Server 2008 R2 Enterprise
SQL Server 2008 R2
BizTalk 2010 beta
ESB 2.1 Toolkit Beta
Share on Facebook

DCPromo kills test BizTalk box.

I needed to run a test to generate a certificate using certificate services, so I had to run my local server dev box as a Domain.  I had to add directory services through the server manager.  I ran the DCpromo.  I ran my certificate tests and proved what I needed to.  Up until this point everythign was done well.
 
However after I was done, I wanted to get back my original user information and test box.  So I DCPromo’ed again, removed the domain and assumed my user would revert to my non-domain "Users" folder.  However once you do the DCPROMO up and back the User ->User mappings fail (this was the same error SQL kept giving me).
 
SQL wouldnt even start anymore and the repair failed.  I can’t log into Biztalk and the Biztalk Groups are missing from my local computer managent- User management.
 
Note to self:  Dont mix to many different kinds of tests.   This is leading me to completely reload the box from scratch, since I was having issues installing the 2.1 ESB tool.   THis is probably a better approach.  On Friday I should have a step by step "building an ESB 2.1 Box from scratch"
 
EDIGUIDANCE Ho!
 
Share on Facebook

Filtering to choose between AS2 and AS2EDI send on non ESB Port Driven Applications

Long story short we had an issue where we needed ot send EDI documents to a customer and AS2 MDN’s to a customer as a response.
The problem was when we started up the AS2 the filters werent properly set.  So every time we created an EDI message out it would send the XML over AS2 (From the AS2 only port) and the complete package EDI packages within AS2EDI send port.
 
Since MDN’s dont have a payload we found that this filter worked well and blocked our EDI sends from goign out the regular AS2 port.
 
Using this in the filter worked out well and remember it isnt a string so just False or True will work on that specific send port filter.
This is strict port binding with no Orchestrations, ESB Guidance etc.  Otherwise,I would suggest an altered Dynamic send port.
 
Share on Facebook

The complete walkthrough of using an inf file to generate a certificate for AS2 via Certificate services.

http://technet.microsoft.com/en-us/library/ff625722%28WS.10%29.aspx

Note this has KeyUsage = 0xA0  ; Digital Signature, Key Encipherment   which is needed by most VAN’s

Keywords:

Generate Key Encipherment certificate

Windows Server

2003 2008 R2

Public private pfx p12

[Version] 

Signature="$Windows NT$"

[NewRequest]
Subject = "CN=www01.fabrikam.com" ; Remove to use an empty Subject name. 
;Because SSL/TLS does not require a Subject name when a SAN extension is included, the certificate Subject name can be empty.
;If you are using another protocol, verify the certificate requirements. 

EncipherOnly = FALSE ; Only for Windows Server 2003 and Windows XP. Remove for all other client operating system versions.
Exportable = FALSE   ; TRUE = Private key is exportable
KeyLength = 2048     ; Valid key sizes: 1024, 2048, 4096, 8192, 16384
KeySpec = 1          ; Key Exchange – Required for encryption
KeyUsage = 0xA0      ; Digital Signature, Key Encipherment
MachineKeySet = True
ProviderName = "Microsoft RSA SChannel Cryptographic Provider"


RequestType = PKCS10 ; or CMC.


[EnhancedKeyUsageExtension]
; If you are using an enterprise CA the EnhancedKeyUsageExtension section can be omitted 

OID=1.3.6.1.5.5.7.3.1 ; Server Authentication
OID=1.3.6.1.5.5.7.3.2 ; Client Authentication

[Extensions]
; If your client operating system is Windows Server 2008, Windows Server 2008 R2, Windows Vista, or Windows 7
; SANs can be included in the Extensions section by using the following text format. Note 2.5.29.17 is the OID for a SAN extension.

2.5.29.17 = "{text}"
_continue_ = "dns=www01.fabrikam.com&"
_continue_ = "dn=CN=www01,OU=Web Servers,DC=fabrikam,DC=com&"
_continue_ = "url=http://www.fabrikam.com&"
_continue_ = "ipaddress=172.31.10.134&"
_continue_ = "email=hazem@fabrikam.com&"
_continue_ = "upn=hazem@fabrikam.com&"
_continue_ = "guid=f7c3ac41-b8ce-4fb4-aa58-3d1dc0e36b39&"


; If your client operating system is Windows Server 2003, Windows Server 2003 R2, or Windows XP
; SANs can be included in the Extensions section only by adding Base64-encoded text containing the alternative names in ASN.1 format.
; Use the provided script MakeSanExt.vbs to generate a SAN extension in this format.

2.5.29.17=MCaCEnd3dzAxLmZhYnJpa2FtLmNvbYIQd3d3LmZhYnJpa2FtLmNvbQ==

[RequestAttributes]
; If your client operating system is Windows Server 2003, Windows Server 2003 R2, or Windows XP
; and you are using a standalone CA, SANs can be included in the RequestAttributes 
; section by using the following text format.

SAN="dns=www01.fabrikam.com&dns=www.fabrikam.com&ipaddress=172.31.10.130"




; Multiple alternative names must be separated by an ampersand (&).

CertificateTemplate = WebServer  ; Modify for your environment by using the LDAP common name of the template.
;Required only for enterprise CAs.
 
 
 
 

Share on Facebook

Back on EDIGuidance Conversion

Starting from scratch since the work arounds didnt pull up the proper properties
Share on Facebook