Referencing PTLoader in Webform that posts to server thru DNWCs fails

Question

I'm running into what appears to be some kind of configuration issue. I'm referencing PTLoader in a Webform to intantiate the Adaptive Portlet Framework. This Webform posts back to the server thru DNWCs. When the postback occurs, I make it to the server, but then it blows up with the following message:
Unable to find Plumtree EDK .NET Web Controls 2.2 Postback script library. Please instll by running the EDK .NET Web Controls 2.2 installer on the imageserver.
The EDK .NET Web Controls 2.2 are installed and work fine so long as I don't refernece PTLoader to intantiate the Adaptive Portlet Framework. Further, when I attempt the following on my local machine, there is no problem. When I elevate the same code to our Development environment I get the error. The Portlet server and image server are on separate boxes in Dev. Any ideas on what I can check?

Answer 1

Thank you Maik,
actually I didn't... I'm using C++ on Qt, which has no reference settings like in Visual Studio (why not VS? About 40k lines of code which we had since before we deployed B1, and was working with B1 since when we deployed B1 in 2008)
I have to either simply use the name (and I only have the 9.0 DI API installed) or the CLSID directly, like in:
   cmp = new QAxObject("SAPbobsCOM.Company", this);
OR
   cmp = new QAxObject("{632F4591-AA62-4219-8FB6-22BCF5F60090}", this);
OR
   cmp = new QAxObject("SAPbobsCOM.Company.90.0", this);
THEN
   cmp->setProperty("Server", "192.168.168.150");
   cmp->setProperty("LicenseServer", "192.168.168.150:30000");
   cmp->setProperty("CompanyDB", db);
   cmp->setProperty("UserName", user);
   cmp->setProperty("Password", pass);
   cmp->setProperty("language", 3); //english
   cmp->setProperty("UseTrusted", false);
   cmp->setProperty("DbServerType", 6); //MSSQL2008
   cmp->setProperty("DbUserName", dbuser);
   cmp->setProperty("DbPassword", dbpass);
   rc = cmp->dynamicCall("Connect()").toInt();
The actual COM is working, as running on the server goes Ok, and when running in the client I can see the client machine "talking" to the server at port 30000 when it gets to "Connect()".
For some reason, when running in the client, it looks like the DI is not accepting that the MS SQL Client is valid.
Thanks again,
Joao S Veiga