The logon provided on Friday, 8/12/2016 1:43 PM by Paragon failed today, 8/16/2016, and was stated as:
"http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.7.2".
Based on other information provided, the following modified logon apparently did work:
"http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.8".
Generated was the content [userid and password redacted]:
<rets replycode="0" replytext="Login Request"><rets-response>
Info=USERID;Character;[usedID redacted]
Info=USERLEVEL;Int;1
Info=USERCLASS;Character;21
Info=AGENTCODE;Character;279144
Info=BROKERCODE;Character;4869
Info=BROKERBRANCH;Character;4869
Info=MEMBERNAME;Character;[name redacted]
Info=MetadataVersion;Character;16.8.17085
Info=MetadataTimestamp;DateTime;2016-08-11T20:45:11.5Z
Info=MinMetadataTimestamp;DateTime;2016-08-11T20:45:11.5Z
Info=TimeoutSeconds;Int;0
Info=VendorName;Character;Black Knight MLS Solutions
Info=ServerProductName;Character;RETS-Paragon
Info=ServerProductVersion;Character;1.0
Info=OperatorName;Character;New England Real Estate Network
GetMetadata=/rets/fnisrets.aspx/NEREN/getmetadata
GetObject=/rets/fnisrets.aspx/NEREN/getobject
Login=http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login
Logout=/rets/fnisrets.aspx/NEREN/logout
Search=/rets/fnisrets.aspx/NEREN/search
</rets-response></rets>
It appears that the Paragon is changing systemic functionality [in this case- version number] without notification which caused the above anomaly. If the absence of such notifications persist, such will frustrate vendor testing the InnoVia to Paragon conversion, which is exacerbated by the lack of InnoVia to Paragon conversion documentation.
Referring to the original question which has not been resolved, and notwithstanding whatever RETS version InnoVia currently uses, the following Innovia search does indeed work:
"http://nne.rets.mlxinnovia.com/nne/Search?SearchType=Office&Class=Office&Select=FirmID,OfficeID,OfficeName&Format=COMPACT-DECODED".
This search yields the following results consisting of 4864 records:
"<rets replycode="0" replytext="Operation Successful">
<delimiter value="09"/>
<columns>FirmID OfficeID OfficeName</columns>
<data>100 0 RE/MAX Black River Realtors</data>
<data>1000 0 Mark Stimson Assoc.</data>
<data>1001 0 Thompson Appraisal Co.</data>
...snip...
<data>9999 0 NEREN</data>
<data>9999 1 NEREN Temporary</data>
<data>I99999 0 Comp Agent</data>
<data>OSIPLI 0</data>
</rets>
The search noted in "Answer #1" from Paragon above does not work:
"http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Search?SearchType=Office&Class=Office&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName&Format=COMPACT-DECODED&rets-version=rets/1.8"
The error message is:
"Server Error
412 - Precondition set by the client failed when evaluated on the Web server.
The request was not completed due to preconditions that are set in the request header. Preconditions prevent the requested method from being applied to a resource other than the one intended. An example of a precondition is testing for expired content in the page cache of the client."
I would appreciate a Paragon example solution that actually works relative to a current Innovia very basic database interrogation.