Forum Replies Created
-
Posts
-
I have found the solution.
I had to install oledb9.0 for analysis servises on the client (where the browser runs). That means I have to do this install on all the potential BAM users 🙁
it looks to me you need read\write permitions on the Folder from where you are receiving location is set.
check the permitions on receiving location?
R-
BizTalk 2006 and HL7A both are same version (i.e Enterprise), not sure seen such problems in some Adapters.
Just my Thought!!
Nar-
Thanks for the reply,
I'm able to install the BizTalk and the 9 databases are created, ( I have a SQL Server 2000 client installed in my PC, and I added my machine name as the server, so I can browse thru the databases)
The error is poped up and the last of configuration, and it will open a VS 2003, Just in time Debugger saying 'An exception 'System.NullReferenceException' has occured in DefaultDomain',
Any help??
Thanks
Vimal K
Not sure, but is BizTalk 2004 supported on 2000 MSDE?
I don’t think it is unless you are using the partner edition.
Might want to double check the help guide.
Don't even get to that. Just launch setup.exe, it initiates the msi package and the error pops up. I don't even get to the EULA.
This could be caused by one of the following:
– your schema isn’t deployed (ie you have an unrecognized message type – namespace#rootnodename)
– you have two schemas deployed anyplace on your system with the same message type
If you don’t know what message type is, it’s one of the main keys BizTalk uses to route message, map messages, and identify data. It’s made up of the namespace, a #, and the root node name.
If these are not unique throughout your system, you will need a custom pipeline for any message receiving those messages. Also, by default using the Xml Receive pipeline BizTalk doesn’t allow unrecognized message. This too is a setting you’ll need a custom pipeline for if you want to change it.
Hope this helps.
Well, not really sure what your problem is. But when I was working with the Oracle Adapter in the past it hard codes the DSN name and procedure names in the auto generated schema.
So, as a starter you might want to try to regenerate your schema if you think those setting might be wrong.
In the past, when I saw that type of error is was because the schema was wrong.
Hope this helps.
Is it trying to connect to the wrong SQL server that isn’t the one you are using for BizTalk?
Just something I’d seen before with something else.
This is how I would go about it:
- Expose your Orchestration as a Web Service to take in your request message and return your result set.
- Create you inbound schema
- Probably just want to use the result from your SQL Query as the return
- Use an Orchestration to query SQL using the SQL Adapter
- Accept an input message with your ID
- Map the input message to your SQL Send Message (Query)
- Get the results and return the message
You should be able to find some separate samples that accomplish all of this and you just have to put them all together. The SDK and online resources are good places to start.
Oh, I’d start with getting the SQL part to work first. It will auto generate schema for you.
I’d expect something like this to take someone new to BizTalk probably a week to complete and understand.
Hope this helps.
You can certainly stop the application hosts before restarting, though in general it shouldn't be strictly necessary, I think. If you are using any out of process adapters (i.e.: http receive, soap receive and so on), you might want to stop the containing processes as well (such as stopping iss) just to be on the safe side as well.
Once you've restarted, you'll always want to check that all services are up and running. Usually, you should've have any problems with receive locations or send ports gertting stopped/disabled after a restart, though I guess it doesn't hurt to check 🙂
To open the help file with VS2005 you need to create a shortcut with this target:
C:\Program Files\Common Files\Microsoft Shared\Help 8\dexplore.exe" /helpcol ms-help://TKH.ScheduledTaskAdapter/ScheduledTaskHelpFile/home.htm
You need to add the adapter, in the Biztalk Admin Console, open the Platform Settings -> Adapters
Then New -> Adapter, give it a name e.g. "Schedule" and select Schedule from the drop down.
The adapter is added to the default host instance, you may like to change this.Create a schema in your project for the trigger message. Make it simple just a root node and a namespace. Generate an instance of this schema
Add a receive port and receive location – select transport type of Schedule -> Configure
Select the schedule property ellipsis and set the schedule to Timespan 5 minutes
Select the task property ellipsis and select XmlStringStreamProivider -> paste the generated instance of the trigger message.
OK…Select XmlReceive Pipeline
In your orchestration set the activate receive shape to receive a trigger message and bind this the orchestration receive port to the receive port just created.
Thanks Greg.. This is exactly what I was looking for. I was thinking about some "out of the box features", but never thought about a custom adapter..
I have installed it for BizTalk 2006 version. I am not able to open the Help File from the installable folder. Could you please let me know can I see how to configure the adapter..?
