Attention, mines: LNK1104: cannot open file ‘c:\Program.obj’

by | Feb 15, 2007 | BizTalk Community Blogs via Syndication

Did you ever see the error message “LNK1104: cannot open file ‘c:\Program.obj'”? No need to say that you are not that kind of a programmer who generates OBJ files in the root of disk C:… So, what’s up and how to fix that?

Either
use short 8.3 path in additional dependencies, or put the long path
into “Linker | General | Additional Library Directories” and simply the
name of the library without path into Additional Dependencies.

I
realize that getting such a message is a sort of shock (I’ve got it
today myself and still feel it :-)), here is the secret:
“C:\Program.obj” is the long path like “C:\Program Files\Microsoft
Platform SDK for Windows Server 2003 R2\Lib” cut after the first space
and appended with the default extension “.obj”.

BizTalk: Architectural Tips: Monitoring orchestration

by | Feb 15, 2007 | BizTalk Community Blogs via Syndication

Note: this orchestration is used for learning purpose. To monitoring in the real life we’d rather use the BAM and BAS. I can see this orchestration in the real environment only as a “lightweight” tool when using an additional technology (BAM/BAS) is not worth the time.




Description:
This is a singleton orchestration for monitoring other BizTalk applications.
It can start/stop by the special “start/stop” message or whatever you want. It can work infinitely or on per day basis, or whatever you want.
It has a direct subscription to the monitoring activity, for example, to some message type, or to the the port name, or some parameters inside the messages.
It can create the log of this activity in a log file or collect this information to create the summary reports.





Implementation details of this sample:

 

 


  • An orchestration uses the sequential convoy to monitor the messages with specific “EDI document type” (it is an element of the all input messages). “Monitor” here means calculating of the message number.
  • It has “per EDI document type” instance. The different orchestration instances are started for different types of monitored messages.
  • The project references another project with monitored message (with schema of this message)
  • The orchestration has one receive port. It has to had parameter the “Ordered Delivery” as “True”. I use parameters the “Binging” as “Direct” and the “Partner Orchestration Port” as “MessageBox”, this simplify the relationship with others applications.



  • It uses one correlation set for two message types: for a monitored message and for a management message. The last one is used for output (trace) the current value of the monitored parameter and for stop the orchestration instance.

    ” LI




I can send you the project files by your request.

 

I would appreciate your feedback.

Windows Vista has problems copying large files

by | Feb 15, 2007 | BizTalk Community Blogs via Syndication

I’ve heard quite a few people complain about the new copying mechanism in Vista but I just chocked them up as anti-MS winers. Well recently it bit me personally. I’ve been connecting to a remote network trying to download large files with no success — Vista simply chokes a ways into the copy process saying “network location no longer available” or something to that effect. Well, sorry Vista, but the network is still available, it’s you with the problem. I switched to an XP box (had to borrow my wife’s laptop since all of my boxes are running Vista now)and everything worked in a snap. Makes me feel great about upgrading!

The Long Tail

by | Feb 15, 2007 | BizTalk Community Blogs via Syndication

Ever since hearing Harry talk about The Long Tail at an architect conference and seeing articles like Architecture Strategies for Catching the Long Tailhit the scenes, I’ve been curious…
So I bought the bookand devoured it.
I usually don’t get into bookson economics but I had so many ah-ha moments with this one, I wanted to share. Great insight into how the Google’s of the world are changing business. The basic premise is that while most businesses (especially the entertainment sector) focus on “hit” products, there is an equally substantial amount of potential revenue in catering to the plethora of “niches” out there (think Google, Netflix, iTunes, eBay, SalesForce.com, etc). As the author puts it, the two basic rules of a Long Tail business are:
  1. Make everything available.
  2. Help me find it.
Aggregation is the key, but aggregation alone isn’t enough with powerful search and ways to navigate the masses of information that cater to my special interests. In terms of software, Microsoft is at the top of The Short Head but they’re desperately trying to make their way down the tail.
The author, Chris Anderson (editor of Wired), keeps up an interesting blog here.

BizTalk: Architectural Tips: Monitoring orchestration

by | Feb 15, 2007 | BizTalk Community Blogs via Syndication

Note: this orchestration is used for learning purpose. To monitoring in the real life we'd rather use the BAM and BAS. I can see this orchestration in the real environment only as a "lightweight" tool when using an additional technology (BAM/BAS) is not worth the time.
Description:
This is a singleton orchestration for monitoring other BizTalk applications.
It can start/stop by the special "start/stop" message or whatever you want. It can work infinitely or on per day basis, or whatever you want.
It has a direct subscription to the monitoring activity, for example, to some message type, or to the the port name, or some parameters inside the messages.
It can create the log of this activity in a log file or collect this information to create the summary reports.

Implementation details of this sample:
  (Pict.)
  • An orchestration uses the sequential convoy to monitor the messages with specific "EDI document type" (it is an element of the all input messages). "Monitor" here means calculating of the message number.
  • It has "per EDI document type" instance. The different orchestration instances are started for different types of monitored messages.
  • The project references another project with monitored message (with schema of this message)
  • The orchestration has one receive port. It has to had parameter the "Ordered Delivery" as "True". I use parameters the "Binging" as "Direct" and the "Partner Orchestration Port" as "MessageBox", this simplify the relationship with others applications.
    (Pict.)
  • It uses one correlation set for two message types: for a monitored message and for a management message. The last one is used for output (trace) the current value of the monitored parameter and for stop the orchestration instance.
    (Pict.)
I can send you the project files by your request.
I would appretiate your feedback.