Hi All

I am using the WCF oracle to connect oracle and execute sp to fetch data.biztalk add -- >Generated Items -->adapter metadat used to generate schemas for oracle sp to be used in map.Till recently it was working fine, But I need extra field(DEP) from oracle has been added to SP in oracle and regenerated the schema at biztalk end,and reloaded the schema in map.Destination schema contains set of shared schemas(complex types)
I have added the DEP field in respective schema. I am able to see both the DEP in sorce and dest schema when I reloaded.

 But I am getting the following error when I test the map.
Exception Caught: The map contains a reference to a schema node that is not valid.  Perhaps the schema has changed.  Try reloading the map in the BizTalk Mapper.  The XSD XPath of the node is: /*[local-name()='<Schema>']/*[local-name()='Stored procedure']/*[local-name()='IO_REFCURSOR']/*[local-name()='IO_REFCURSORRECORD']/*[local-name()='DEP']

Please let me know your suggestions.

Thanks
Krishna

Just to make sure, did you:

1) Close and re-open the mapper window, without any errors
2) Rebuild
3) maybe repeat 1)

?

thanks for your response,

 

I did all earlier, but no luck.

 

Thanks

Krishna

Hi all,

I able to find out the what issue is Destination schema contains set of shared schemas(complex types)
when I opened the destination schema and try to generate instance, newly added field is not present. in output file

and when I validate map it gives me following error

Exception Caught: Cannot load source/destination schema: Destination schema.  Either the file/type does not exist, or if a project dependency exists, the dependent project is not built. 

I have built the schemas project , but still the same issue

Thanks

Krishna

Are you able to open Biztalk Mapper window in Visual studio?
You might be missing some assembly which contains dependency of schema or any other dependancy required inside map.

Also check if this hotfix is helpful to you: http://support.microsoft.com/kb/326578

 

First of all remove the old schema assembly from the GAC. Try to clean the schema project build and rebuild it again. Then add the reference to your map project. In the transform shape (orchestration) see if the schemas are still valid and there is no error. Open the map again and see that the links are valid. Test and validate the map again.

If the map project isn't caching the old assembly the problem should go away. For this use the above given steps.

Right click on the map and select "Open with - Xml Editor", sometimes it will be easy to spot broken links this way

Thanks for your response,

I didi the above steps , Interesting thing is I am able to see field in output file from generate instance of destination schema (whcih I couldn't ealrier).

But when I test/validate with new added link to map I see the following error

Exception Caught: The map contains a reference to a schema node that is not valid.  Perhaps the schema has changed.  Try reloading the map in the BizTalk Mapper.  The XSD XPath of the node is: /*[local-name()='<Schema>']/*[local-name()='Stored procedure']/*[local-name()='IO_REFCURSOR']/*[local-name()='IO_REFCURSORRECORD']/*[local-name()='DEP']

 

thanks

Krishna

It could be possible that it might be refering to the wrong Schema Assembly . To test you can make a Test Application and add the reference of the assembly containing the schema and add new Map and apply same/some login and  try to validate and see if you recieve the correct output . But before doing that make sure you unGac and the ReGac the assembly ,also make sure that there is no assembly in the temp folder of GAC with the same Name (make sure to remove if any assembly is present in the Temp

Most of your cases, i guess this may be reason.

there will be a cs file for every schemas auto generated in the visual studio. when ever you change ur main schema, some times the related cs file may not get updated. when build the proj with old schema cs file, this error occurs.

Resolution: deleted the auto generated cs file for the schema and rebuild it.

I hope this may solve some one issue

Thanks,

Manjunath

And its may be accrue..!

if your schema's in one application and Mapper in another application,

if you add schema reference in mapper application,

you need to delete that update that reference.! or replace that reference.

I hope this may solve some one issue

Thanks 

Krishna,

What worked finally?