|
Home > Archive > BizTalk Server Tools > September 2005 > Invalid Class String
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Invalid Class String
|
|
| mnagisetty 2005-08-29, 5:56 pm |
| I ran across this issue in BizTalk Explorer after uninstalling the BizTalk
adapter for MQ Series on my BizTalk machine. I am not sure what is actually
causing the error. Here is how the error could be recreated:
1) Open Visual Studio .NET
2) Open BizTalk Explorer
3) Expand any artifact group (Orchestrations, Send Ports, Send Port Groups,
etc)
4) Click on any artifact instance and try to go to Properties
or try to create a new instance of a Port/Location.
5) I get a popup window which reports "Invalid Class String"
I am still able to create and bind ports using binding files and the
deployment wizard. However, BizTalk Explorer is pretty much useless at this
point. I CANNOT change bindings on orchestrations, create new ports or do
anything useful in BizTalk Explorer.
Any help is greatly appreciated.
| |
| Matt Milner 2005-08-29, 5:56 pm |
| You might try checking the registry for remaining configuration information
about the adapter and you might also check in the mgmt db for remnants
there. If you have adapter settings it might be trying to do some lookups
or initialization or something on classes that have been removed.
HTH,
Matt
"mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
news:46D1F6C5-502C-48E1-9ABF-2019C7A258E7@microsoft.com...
>I ran across this issue in BizTalk Explorer after uninstalling the BizTalk
> adapter for MQ Series on my BizTalk machine. I am not sure what is
> actually
> causing the error. Here is how the error could be recreated:
>
> 1) Open Visual Studio .NET
> 2) Open BizTalk Explorer
> 3) Expand any artifact group (Orchestrations, Send Ports, Send Port
> Groups,
> etc)
> 4) Click on any artifact instance and try to go to Properties
> or try to create a new instance of a Port/Location.
> 5) I get a popup window which reports "Invalid Class String"
>
> I am still able to create and bind ports using binding files and the
> deployment wizard. However, BizTalk Explorer is pretty much useless at
> this
> point. I CANNOT change bindings on orchestrations, create new ports or do
> anything useful in BizTalk Explorer.
>
> Any help is greatly appreciated.
| |
| mnagisetty 2005-08-30, 5:58 pm |
| Thanks for the suggestions. I looked in the registry and found the following
key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bi
zTalk Server 2004 Adapter for
MQSeries
Although, knowing this key is not much help to me at this point. I've had
to reinstall the adapter after reinstalling Webpshere MQ.
I also looked at the BizTalkMgmtDb database. I found that the adm_Adapter
table contains an entry for MQSeries. This table also contains the following
columns: Capabilities, MgmtCLSID, InboundEngineCLSID, and
OutboundEngineCLSID. The capabilities column seems to have the same value as
the SQL adapter. Is that a problem?
Also, do the CLSID columns need to correlate to a class ID from some
registry key?
I also noticed that the adm_ReceiveHandler, admReceiveLocation, and
adm_SendHandler tables have a foregin key relationship to the adm_Adapter
table.
Does this information help in any way? I am a bit wary about modifying
values in the DB this way. There must be a better way to deal with this
issue.
"Matt Milner" wrote:
> You might try checking the registry for remaining configuration information
> about the adapter and you might also check in the mgmt db for remnants
> there. If you have adapter settings it might be trying to do some lookups
> or initialization or something on classes that have been removed.
>
> HTH,
> Matt
>
>
> "mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
> news:46D1F6C5-502C-48E1-9ABF-2019C7A258E7@microsoft.com...
>
>
>
| |
| Matt Milner 2005-08-31, 5:58 pm |
| Well, the best way to deal with this is to open a call with Microsoft PSS
and have them tell you what to do. 
If you have reinstalled the adapter and are still getting errors, then I'm
not sure what your problem would be. If you have uninstalled the adapter
and are trying to remove it to get rid of errors, then the rest of this
message might be helpful, but otherwise you'll probably want to ignore it.
First, have you gone into the BizTalk Server Administration console to see
if the adapter is listed there? If so, then you might try deleting the
adapter from there and restarting your system if that doesn't do it right
away. You'll need to make sure you don't have any receive locations or send
ports using this adapter before being able to delete it. This should clean
up the database portion, which might take care of your problem all together.
The other thing you can try is to reinstall and remove the adapter again to
see if you get a cleaner uninstall the second time.
hth,
Matt
"mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
news:E9FB4C9A-A135-4C1B-AC7C-0A2AEBEB4373@microsoft.com...[vbcol=seagreen]
> Thanks for the suggestions. I looked in the registry and found the
> following
> key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bi
zTalk Server 2004 Adapter for
> MQSeries
>
> Although, knowing this key is not much help to me at this point. I've had
> to reinstall the adapter after reinstalling Webpshere MQ.
>
> I also looked at the BizTalkMgmtDb database. I found that the adm_Adapter
> table contains an entry for MQSeries. This table also contains the
> following
> columns: Capabilities, MgmtCLSID, InboundEngineCLSID, and
> OutboundEngineCLSID. The capabilities column seems to have the same value
> as
> the SQL adapter. Is that a problem?
> Also, do the CLSID columns need to correlate to a class ID from some
> registry key?
> I also noticed that the adm_ReceiveHandler, admReceiveLocation, and
> adm_SendHandler tables have a foregin key relationship to the adm_Adapter
> table.
>
> Does this information help in any way? I am a bit wary about modifying
> values in the DB this way. There must be a better way to deal with this
> issue.
>
>
> "Matt Milner" wrote:
>
| |
| Marvin Smit 2005-08-31, 5:58 pm |
| Hi,
I was just wondering.... Can you still use the BTSCatalogExplorer OM
to browse through this info?
Would help determine whether the BT engine & DB have an issue or if
its the "Tool integrated into VS" that is causing this.
Hope this helps,
Marvin Smit.
On Mon, 29 Aug 2005 13:44:25 -0700, "mnagisetty"
<mnagisetty@discussions.microsoft.com> wrote:
>I ran across this issue in BizTalk Explorer after uninstalling the BizTalk
>adapter for MQ Series on my BizTalk machine. I am not sure what is actually
>causing the error. Here is how the error could be recreated:
>
>1) Open Visual Studio .NET
>2) Open BizTalk Explorer
>3) Expand any artifact group (Orchestrations, Send Ports, Send Port Groups,
>etc)
>4) Click on any artifact instance and try to go to Properties
>or try to create a new instance of a Port/Location.
>5) I get a popup window which reports "Invalid Class String"
>
>I am still able to create and bind ports using binding files and the
>deployment wizard. However, BizTalk Explorer is pretty much useless at this
>point. I CANNOT change bindings on orchestrations, create new ports or do
>anything useful in BizTalk Explorer.
>
>Any help is greatly appreciated.
| |
| mnagisetty 2005-09-01, 5:55 pm |
| There may be some truth to what you are saying because I actually did remove
and reinstall the adapter so the issue should have been fixed. Another
detail I didn't mention before:
When I double click on a port or orchestration then the messagebox window
has a title of "Microsoft Development Environment". If I right-click and go
to edit, the messagebox window has a title of "BizTalk Explorer". However
the contents of both popup windows are the same: "Invalid Class String".
The above information may be a little silly....maybe it is useful for
determining who is throwing the error...Does this help in in any way?
Anyways, I will try what you suggested: remove any ports that reference the
adapter, remove and uninstall the adapter and then reinstall. Will let you
know if that works.
Thanks
Monish
"Matt Milner" wrote:
> Well, the best way to deal with this is to open a call with Microsoft PSS
> and have them tell you what to do.
>
> If you have reinstalled the adapter and are still getting errors, then I'm
> not sure what your problem would be. If you have uninstalled the adapter
> and are trying to remove it to get rid of errors, then the rest of this
> message might be helpful, but otherwise you'll probably want to ignore it.
>
> First, have you gone into the BizTalk Server Administration console to see
> if the adapter is listed there? If so, then you might try deleting the
> adapter from there and restarting your system if that doesn't do it right
> away. You'll need to make sure you don't have any receive locations or send
> ports using this adapter before being able to delete it. This should clean
> up the database portion, which might take care of your problem all together.
>
> The other thing you can try is to reinstall and remove the adapter again to
> see if you get a cleaner uninstall the second time.
>
> hth,
> Matt
>
>
>
>
> "mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
> news:E9FB4C9A-A135-4C1B-AC7C-0A2AEBEB4373@microsoft.com...
>
>
>
| |
| mnagisetty 2005-09-12, 6:02 pm |
| Well, I tried what you said: Uninstall the adapter, etc. I am still getting
the same error. Any other ideas?
"Matt Milner" wrote:
> Well, the best way to deal with this is to open a call with Microsoft PSS
> and have them tell you what to do.
>
> If you have reinstalled the adapter and are still getting errors, then I'm
> not sure what your problem would be. If you have uninstalled the adapter
> and are trying to remove it to get rid of errors, then the rest of this
> message might be helpful, but otherwise you'll probably want to ignore it.
>
> First, have you gone into the BizTalk Server Administration console to see
> if the adapter is listed there? If so, then you might try deleting the
> adapter from there and restarting your system if that doesn't do it right
> away. You'll need to make sure you don't have any receive locations or send
> ports using this adapter before being able to delete it. This should clean
> up the database portion, which might take care of your problem all together.
>
> The other thing you can try is to reinstall and remove the adapter again to
> see if you get a cleaner uninstall the second time.
>
> hth,
> Matt
>
>
>
>
> "mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
> news:E9FB4C9A-A135-4C1B-AC7C-0A2AEBEB4373@microsoft.com...
>
>
>
| |
| Matt Milner 2005-09-18, 2:48 am |
| Hmm, not without going into the database and manually removing all of the
data related to the adapter and going into the registry to do the same. I'd
say PSS is your best bet at this point.
Matt
"mnagisetty" <mnagisetty@discussions.microsoft.com> wrote in message
news:01C572FB-0820-457C-876F-B2A691E86BB1@microsoft.com...[vbcol=seagreen]
> Well, I tried what you said: Uninstall the adapter, etc. I am still
> getting
> the same error. Any other ideas?
>
> "Matt Milner" wrote:
>
|
|
|
|
|