Filed under BPI
Tagged as BizTalk, BPI, ESB, SQL
When I opened the ESB.Portal (BizTalk ESB Guidance 2.0) in Internet Explorer I ran into the next problem:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 27-3-2009 20:26:37
Event time (UTC): 27-3-2009 19:26:37
Event ID: f5247af6841e45349be4dbd365417ff9
Event sequence: 99
Event occurrence: 4
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1/ROOT/ESB.Portal-1-128826538435234595
Trust level: Full
Application Virtual Path: /ESB.Portal
Application Path: C:\projects\microsoft.practices.esb\Source\Samples\Management Portal\ESB.Portal\
Machine name: myMachine
Process information:
Process ID: 5752
Process name: w3wp.exe
Account name: NT AUTHORITY\NETWORK SERVICE
Exception information:
Exception type: SqlException
Exception message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 – No connection could be made because the target machine actively refused it.)
Request information:
Request URL: http://localhost/ESB.Portal/Lists/RegistrySummaryContainer.aspx
Request path: /ESB.Portal/Lists/RegistrySummaryContainer.aspx
User host address: ::1
User: myMachine\user
Is authenticated: Trueetc etc |
To fix this you must make sure your SQL connections are configured properly, like:
TCP/IP must be enabled!
Filed under BPI
Tagged as BizTalk, BPI, HL7
The latest HL7 version in BizTalk Server 2009 is 2.5. The newest version is v3.0 and is ‘official’ since 2005. Vendors however are not investing on the new standard, because they invested several years ago in the 2.x standard for their software. So it will take a long time before this new standard is adopted by the market.
The Dutch government implemented HL7 v3.0 standard for the Electronic Health Record (AKA ‘Aorta’). This is a subset from the official ‘standard’ and customized for the Dutch Healthcare (so ‘we’ created our own Xsd’s). Lately I was on the Dutch Health and IT event, and on a seminar there was told that the v3.0 (Xsd’s) is difficult to implement, because it will fail for code generation. Also for BizTalk Server 2009 I had problems with this, so more time has to be spend on this.
I hope to inform you very soon on my progress on this.
===============================
(Dutch version)
De laatste HL7 versie in BizTalk Server 2009 is 2.5. Zo ook in BizTalk Server 2009. De nieuwste versie is v3.0 en is ‘officieel’ sinds 2005. Leveranciers zijn echter niet happig op het investeren in deze nieuwe standaard, omdat ze een aantal jaren terug geïnvesteerd hebben in de 2.x standaard voor hun software. Het zal dus nog een tijdje duren voordat deze nieuwe standaard toegepast zal worden op de markt.
De Nederlandse overheid heeft voor het Electronisch Patiënten Dossier (EPD) HL7 v3.0 geïmplementeerd (ook wel bekend als ‘Aorta’). Dit is een subset van de officiële standaard en aangepast op de Nederlandse zorg (‘we’ hebben dus onze eigen Xsd’s gemaakt). Laatst heb ik de Zorg&ICT beurs bezocht, en daar werd tijdens een mini congres verteld dat v3.0 Xsd’s lastig zijn om te implementeren, omdat code generatie hierop niet zal werken. Ik heb dit zelf ook met BizTalk Server 2009 ondervonden. Daar zal dus meer tijd in gestoken moeten worden.
Ik hoop jullie binnenkort verder te informeren over mijn voortgang.
Filed under BPI
Tagged as BizTalk, BPI, ESB
I run into the next problem with BizTalk Server 2009 Beta:
Delete of ApplicationNode failed.
I tried to manual remove the application, but somewhere it’s holding references to non existing resources. This exact message doesn’t give a hit in Google.
UPDATE: Thiago Almeida pointed me on a missing Dll in the GAC. After verifying this, this seems to be the case. After putting all Microsoft.Practices.ESB.Resolver* Dll’s back in the GAC (and a reboot) I was able to remove the application. In the first place I installed the ESB Guidance from the binaries. Later on I uninstalled the ESB, so I could install the ESB and the samples from source code. Probably with the uninstall the application was not removed from BizTalk and still referenced the ‘old’ Dll’s, or the problems occurred because of some manual actions by me after that. Who can tell?
This update is also a nice example what Twitter can mean to you 
Cheers!
Filed under BPI
Tagged as BizTalk, BPI, ESB
Be aware of the difference, because they use a different strong name key as described in the Installation Instructions. It is also noticed on Codeplex.
It is a pity that the sample source code is running also into several errors regarding ‘different’ dll’s.
Just to share with you:
Error
Exception calling "SaveChanges" with "0" argument(s): "Unable to locate assembly "Microsoft.Practices.ESB.Resolver, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"."
At C:\projects\microsoft.practices.esb\Source\Core\Install\Scripts\ESBFunctions.ps1:350 char:28
+ $null = $exp.SaveChanges( <<<< )
Error
Exception calling "SaveChanges" with "0" argument(s): "Unable to locate assembly "Microsoft.Practices.ESB.Resolver, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"."
At C:\projects\microsoft.practices.esb\Source\Core\Install\Scripts\ESBFunctions.ps1:350 char:28
+ $null = $exp.SaveChanges( <<<< )
At the end the easiest way is to install from source code. If you install from the binaries, then you have to make sure your samples are referencing the right assemblies.
Filed under BPI
Tagged as BizTalk, BPI
I created a schema project without strong name. When I build this project I get these messages:
"cannot resolve the ’schemaLocation’ attribute"
When I add a strong name, then these messages disappear and I get the next warnings:
“The field ‘namespace.project.schemaname.__DummyVar0′ is never used”
This is default behavior in BizTalk Server 2009 Beta. I didn’t figure how I can resolve this.
If you know, please let me know.
Filed under BPI
Tagged as IW, Presentations
On this link you find all the sessions from MIX09: http://blogs.msdn.com/mswanson/pages/MIX09Sessions.aspx
Its all about Silverlight, Windows 7, Internet Explorer 8, ASP 4.0, REST, ASP 4.0, etc etc
Not real a BPI thing, but good to know what’s out there. And important who are working for the other BPI
Filed under BPI
Tagged as BizTalk, BPI, ESB, PowerShell
When running the ‘setup_bin.cmd’ from the folder ‘C:\projects\microsoft.practices.esb\Source\Samples\DynamicResolution\Install\Scripts’ I receive the message:
File C:\projects\microsoft.practices.esb\Source\Samples\DynamicResolution\Install\Scripts\DynamicResolution_Install.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see "get-help about_signing" for more details.
At line:1 char:32
+ .\DynamicResolution_Install.ps1 <<<< domainname\username ‘password‘ 1
On a development machine you can run on a DOS Command Prompt the next command:
powershell Set-ExecutionPolicy Unrestricted
After that the setup_bin.cmd will run just fine.
Filed under BPI
Tagged as BAM, BizTalk, BPI
I posted recently a problem with BAM: “Error deploying definition to BAM”. With the ESB Guidance 2.0 (CTP version from January) I received the same message, but then for the database BAMStarSchema. After adding the SQL Service account to the right security group I received another error:
Microsoft (R) Business Activity Monitoring Utility Version 3.8.104.5
Copyright (C) 2006 Microsoft Corporation. All rights reserved.
Using ‘BAMPrimaryImport’ BAM Primary Import database on server ‘WIN2008′…
Deploying Activity… Done.
Deploying View… ERROR: The BAM deployment failed.
Server: The operation has been cancelled.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘ExcByApplication_ExcDatetime’, Name of ‘ExcByApplication_ExcDatetime’ was being processed.
Errors in the OLAP storage engine: An error occurred while the ‘Year’ attribute of the ‘ExcByApplication_ExcDatetime’ dimension from the ‘BAMAnalysis’ database was being processed.
Internal error: The operation terminated unsuccessfully.
The following system error occurred: Unspecified error .
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘bam_ExcByApplication’, Name of ‘bam_ExcByApplication’.
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of ‘ExcByApplication_ExcDatetime’, Name of ‘ExcByApplication_ExcDatetime’ was being processed.
… etc …
After inspecting my machine I find out that I was missing BAMAnalysis. After reconfiguring BizTalk again, it worked fine. Note: to trigger to create the BAMAnalysis was to rename it to another name, and then back to BAMAnalysis.
Filed under BPI
Tagged as BAM, BizTalk, BPI
I’m working on a demo PC for our company. In one of the scenarios I’m using BAM. I didn’t use it for a quiet long time. Also with BizTalk Server 2009 Beta BAM is still a powerful tool for generating near real-time management information.
But why am I restricted to 18 characters for the BAM View name or Measure name?
A colleague of my who is a BI specialist doesn’t recognize this with SQL Server Analysis Services. So SQL Server has not this kind of restriction.
Filed under BPI
Tagged as BAM, BizTalk, BPI
I created a BAM Activity Definition in Excel 2007: SomeView.xml. This file can be deployed with BM like:
BM deploy-all -definitionfile:SomeView.xml
In the DOS-box I received the output:
Deploying Activity… Done.
Deploying View… ERROR: The BAM deployment failed.
OLE DB error: OLE DB or ODBC error: Cannot open database “BAMPrimaryImport" requested by the login. The login failed.; 42000.
Errors in the high-level relational engine. A connection could not be made to the data source with the DataSourceID of ‘bam_rta_SomeView’, Name of ‘bam_rta_SomeView’.
Server: The operation has been cancelled.
On the Internet I couldn’t find this message in conjunction with the BAMPrimaryImport database. When looking in the EventLog I saw the next Informational message:
Login failed for user ‘mymachine\myserviceaccount’. Reason: Failed to open the explicitly specified database. [CLIENT: <named pipe>]
After adding this account to the BAMPrimaryImport database with the right access, it worked all fine:
Deploying Activity… Done.
Deploying View… Done.
Deploying Security… Done.
Did I missed something during installation, or is it because I used BizTalk Server 2009 Beta?
