Hi, Stephen -

PB 2022 was produced with a newer version of Visual Studio than previous versions. Have you distributed the newer Microsoft runtime files? Below is the updated information from the PB Help topic "runtime files":

These files will be present on the machine(s) where the PB IDE is installed, but may not be available on other machines.

Best regards, John

Hi Stephan;

  You should no longer be using PBNI for things like this. Only the corresponding PBD file only. My guess is that there are some old PBDOM objects in one of your PB App's PBL's left over from an old PBX PBNI import. That could easily cause the issue that you described. Check your App's PBL'S & remove any PBDOM objects. Then proceed with the PBDOM220.pbd in the library list only approach.

HTH

Regards... Chris 

PBDOM220.PBD contains PBNI objects which refer to C++ code located in PBDOM.pbx.

Thank you all for your answers!

I checked all my pbls for using pbdom objects. I never imported a pbx file, pbdom220.pbd is in the library list  (the original from ..Powerbuilder 22.0\IDE path).Now all the Microsoft files on the list (Thank you John!) are now in the list of external files.

 Does PB DOM has to be checked in the list of runtime files? PB Help says: required for PBDOM.PBX So I unchecked it now.

I disabled all paths to prior installations and runtimes. 

I pushed pbdom220.pbd to the beginning of the library list, trying, if there was a difference 

After compiling and uploading the same issue and error message. But not while running in IDE 32/64.

generating an .EXE File and run it outsout IDE, I get an error "Reference to an invalid object" at  the first line of

CATCH ( PBDOM_Exception pbde )
   MessageBox( "PBDOM Exception", pbde.getMessage() )
CATCH ( PBXRuntimeError re )
   MessageBox( "PBNI Exception", re.getMessage() )
END TRY

Is there something missing?

Stephan

Still not running.... 

- PBDOM220.pbd from path Appeon\Powerbuilder 22.0\IDE is in the library list
- Envrironment path Variables first point to Version 22.0 Files (to make shure to get the right ones)

For testing

- inserted code for a log to a file while parsing document
- generating a client deployment package to upload on a new clean webserver (64 bit and later 32 bit, no difference, same behavior)
- executing deployment package, controlling pbdom220.pbd folder, c++ runtime files mentioned above exist

executing application 

opening a XML File for parsing

"Error Calling method of an pbni object" message 

In LOG FIle:

After
           lpdom_builder = CREATE BUILDER
it runs into

       Catch PBXRuntimeError

Running same out of IDE, all works fine (32 bit or 64 bit)

Can't find any old modules.... any ideas?

Hi, just in case:

If you are using PFC classes, then - depending on which version of it - there might be pbdom objects copied into them. So that means you would have duplicate objects if you hook up the pbdom.pbd.

Depending on which library is listed first, one or the other would be used.

regards.

another try...
I just made a simple new project with one object containing simple Getfileselect and Calling fu_file_read_xml(ps_filename)

In library list only included pbdom220.pbd 

Same problem "PBNI_Exception": "Error calling method of a PBNI object". In IDE it runs without problems.

You can download and install this via https://tw8.thermis.de/TESTXML

There is a sample XML "Heiko 2017.XML" included. 

What is wrong?

Best regards 

Stephan

Code of fu_file_read_xml(ps_filename) as follows

PBDOM_Builder lpbdom_Builder
PBDOM_Document lpbdom_Doc
PBDOM_Object lpbdom_Obj[]
PBDOM_Element lpbdom_Element
PBDOM_Attribute lpbdom_Attribute

integer li_Counter, li_Max, li_count
string ls_Text, ls_parseErrors[], ls_name, ls_objectclass
string ls_version, ls_encoding, ls_standalone
long ll_ret
long ll_objectclass
boolean lb_parse
boolean lb_state




ll_ret = XMLParseFile(ps_filename) // adds .log add end


IF ll_ret = 0  THEN

	TRY

		lpbdom_Builder = CREATE PBDOM_BUILDER

	// Import File and generate XML
		lpbdom_Doc = lpbdom_Builder.BuildFromFile( ps_filename )
		lb_parse = lpbdom_Builder.GetParseErrors(ls_parseErrors)
		IF lb_parse THEN
			FOR li_count = 1 TO Upperbound(ls_parseErrors)
				MessageBox("ParseError",ls_parseErrors[li_count])
			NEXT
		END IF
		IF isValid (lpbdom_Doc) THEN
			lpbdom_Doc.getxmldeclaration (ls_version, ls_encoding, ls_standalone)
			IF lpbdom_Doc.HasChildren() THEN
				IF lpbdom_Doc.GetContent( lpbdom_Obj ) THEN
				// Get 1st Level data
					li_Max = UpperBound( lpbdom_Obj )
				   	FOR li_count = 1 TO li_max
						ls_objectclass = lpbdom_Obj[li_count].GetObjectClassString() 
						ll_objectclass = lpbdom_Obj[li_count].GetObjectClass()
						IF ll_objectclass = TPBDOM_ELEMENT THEN
							ls_name =  lpbdom_Obj[li_count].GetName()
							ls_Text =   lpbdom_Obj[li_count].GetText()
							lpbdom_Element = lpbdom_Obj[li_count]
							IF ls_name = "Road" THEN
								IF lpbdom_Element.HasAttributes() THEN
									lpbdom_Attribute = lpbdom_Element.getAttribute("Version")
									is_xml_version = lpbdom_Attribute.GetText()
									ii_road_version = integer(is_xml_version)
									MessageBox("Success","Version = " + string(ii_road_version))
								END IF
//								fu_parse_road(lpbdom_Element,ps_filename)
							END IF
						END IF
					NEXT
				END IF
			END IF
		END IF
		CATCH (PBDOM_Exception lpbdom_Except)
		 	MessageBox( "PBDOM_Exception", lpbdom_Except.GetMessage())
		CATCH (PBXRuntimeError re)
		 	MessageBox( "PBNI_Exception", re.GetMessage())
		END TRY
	

	
	DESTROY lpbdom_Builder
	lb_state = TRUE
ELSE
	lb_state = FALSE
END IF



RETURN lb_state

Hi Roland and Chris

I just found a difference from my 2022 to my PB2021 workspace:
In the Output/Default Window of the IDE there are tow entries which do not exist in 2021:

(See attached Screenshots)

maybe this causes my problems with PBDOM after deploying?

Where di they come from? I searched all informations about Output window in the IDE description of PB Help and Appeon Wwebsite, but didn't find any further informations.

Best regards 

Stephan

We had the same problem when migrating from PB2019 to PB2022.

I traced it down to a new dependency on PBXerces.dll and xerces-c.dll .

Once we added these files to our application, it worked again.