The BizTalk SDK documentation shows the property page name should be
in the form:

BizTalk_ComponentName_1.asp
BizTalk_ComponentName_1_post.asp

I'm unable to get my .NET component's property page to display from
Messaging Manager. It says "property page unavailable". The AIC works
fine otherwise, so I know the problem is with the property pages and
not the component itself.

I tested with the SAP App Integration page and it came up fine, so I
know that at least some property pages work.

The official COM ProgID of the component is:

DocSpecToSql.InsertAIC

So what is the correct name of the property page?

Messaging Manager (in both the port and channel) shows the name as:

DocSpecToSql InsertAIC

I assume that's a space between the assembly and class names. I have
tried every combination of characters I can think of to get the name
to match but Messaging Manager always says the property page is
unavailable.

I tried using a dot (.), space, no space, an underscore; none of them
made a difference. I also tried using just DocSpecToSql and just
InsertAIC but that didn't help either. I even named the file with %20
instead of the space and that didn't work. Also tried matching the
component filename (DocSpecToSQL-AIC.DLL), which also didn't work.
Based on some other messages in this group I tried all of the above
without the _1 suffix.

As always, any insights are welcome.

-- Craig Yellick

[ Post a follow-up to this message ]

Hi Craig,

If I remember correctly for dot net components the asp file names need to
incorporate the complete namespace for your AIC with the dots replaced with
underscores.

If that still doesn't help the name of the asp page that the messaging
manager is requesting should be logged in the IIS log on your biztalk server
in c:\windows\system32\logfiles\

hope this helps
richard



"Craig Yellick" <CraigGoogle@Yahoo.com> wrote in message
news:181a3bdc.0403091427.1301d86@posting.google.com...
> The BizTalk SDK documentation shows the property page name should be
> in the form:
>
>   BizTalk_ComponentName_1.asp
>   BizTalk_ComponentName_1_post.asp
>
> I'm unable to get my .NET component's property page to display from
> Messaging Manager. It says "property page unavailable". The AIC works
> fine otherwise, so I know the problem is with the property pages and
> not the component itself.
>
> I tested with the SAP App Integration page and it came up fine, so I
> know that at least some property pages work.
>
> The official COM ProgID of the component is:
>
> DocSpecToSql.InsertAIC
>
> So what is the correct name of the property page?
>
> Messaging Manager (in both the port and channel) shows the name as:
>
> DocSpecToSql InsertAIC
>
> I assume that's a space between the assembly and class names. I have
> tried every combination of characters I can think of to get the name
> to match but Messaging Manager always says the property page is
> unavailable.
>
> I tried using a dot (.), space, no space, an underscore; none of them
> made a difference. I also tried using just DocSpecToSql and just
> InsertAIC but that didn't help either. I even named the file with %20
> instead of the space and that didn't work. Also tried matching the
> component filename (DocSpecToSQL-AIC.DLL), which also didn't work.
> Based on some other messages in this group I tried all of the above
> without the _1 suffix.
>
> As always, any insights are welcome.
>
> -- Craig Yellick

[ Post a follow-up to this message ]

Thanks!

Here's the scoop on .NET components and AIC property pages:

Take the full assembly + class name, replace all dots with
underscores, do not use the BizTalk_ prefix or a _1 sufffix as
illustrated in the BizTalk SDK and all of the property pages that are
pre-installed in the Messaging Manager's pipeline directory.

So, my ProgID of:

DocSpecToSQL.InsertAIC

Uses property page:

DocSpecToSQL_InsertAIC.asp

How simple is that? Sheesh. Wait until you see what I did get a
definitive answer. Your idea about looking in the web access log got
me on the right track.
Of course Messaging Manager never makes a simple request. Instead it
calls a ProcessRequest.asp that handles all requests.

So I open up the file… what a complex machine. But I do find where
requests are ultimately processed, so I stick this in the code:

xmlRequestDoc.Save "C:\temp\processRequest.xml"

Aha! I get to watch Messaging Manager make requests! Great fun but it
turns out that requests for property pages do no go through this
beast. Another trip to the log file and I see that:

pe_show_props.asp

gets called when the Property button is pressed. As before, the source
code is complex beyond comprehension but I do find a spot where the
URL is built. There's a ton of error handling in this could but do you
think they'd bother to let you know the name of the file that's
missing? Nope. I tried to address that shortcoming but gave up, too
complex in there and I've got no time for this. So instead I tossed
the URL out to a file, like so:

dim fso,h
set fso = Server.CreateObject("Scripting.FileSystemObject")
set h = fso.CreateTextFile("C:\temp\propPageReq.txt",true)
h.writeline(g_sUrl)
h.close()

Finally! My property page is working. Sheesh.

-- Craig Yellick


"richard" <reply@tonewsgroup.com> wrote in message news:<ufMf1LoBEHA.140@TK2MSFTNGP09.phx.g
bl>...
> Hi Craig,
>
> If I remember correctly for dot net components the asp file names need to
> incorporate the complete namespace for your AIC with the dots replaced wit
h
> underscores.
>
> If that still doesn't help the name of the asp page that the messaging
> manager is requesting should be logged in the IIS log on your biztalk serv
er
> in c:\windows\system32\logfiles\
>
> hope this helps
> richard
>
>
>
> "Craig Yellick" <CraigGoogle@Yahoo.com> wrote in message
> news:181a3bdc.0403091427.1301d86@posting.google.com... 

[ Post a follow-up to this message ]