Premise Change HostAddress on default website?

Motorola Premise

samgreco

Active Member
So I am doing some cleanup and trying to install John in VA's new PremiseMetro version and running into an issue.  Not sure how it happened or how to fix it.
 
My server's IP address is 192.168.0.210.  BUT the Premise website show their default website addresses as 192.168.226.1.  But the addresses in the Builder are grayed out and will not allow me to change them.
 
Where do I change it?
 
Nevermind.  I stopped it, deleted the ports and when I put the port info back in, it pulled in the correct address.
 
So I figured out where it is coming from.  It's the VMWare virtual NIC.  For some reason, Premise keeps reseting to THAT NIC as it's default address.  Anyone have a clue how to change that behavior?
 
Is your Premise server a VMWARE guest?  If so, does VMWARE guest see it's NIC and the hosts NIC or are their multiple NIC's available to the guest?  If the latter, you may want to consider removing one of the NICs or setting the binding order to get the behavior you want.  The former seems like it may be a VMWARE setting to not publish the host's NIC into the guests.
 
Premise is on the host.  But I just found that the 2 VMWare NICs that were installed (one for NAT and the other for Host) are not needed since I am running all of my guests in Bridged mode.  So I have now solved the ghost IP address.
 
But I still can't get Web Services/PremiseMetro to work.  I keep getting Configuration error occurred, etc.  Tht log only shows the following:
 

2015-01-20 20:30:26,468 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services OnStart command received. Worker thread starting
2015-01-20 20:30:26,479 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services worker thread started
2015-01-20 20:30:26,498 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver Server method started
2015-01-20 20:30:26,512 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.0.210
2015-01-20 20:30:26,512 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 127.0.0.1
2015-01-20 20:30:26,537 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost created using service URL: net.tcp://Holly:8888/PremiseWebService
2015-01-20 20:30:26,538 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver NetTCPBinding created
2015-01-20 20:30:26,538 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost endpoint added
2015-01-20 20:30:26,538 [7] INFO - [PremiseWebServicesDriverLogger] Starting metadata service on: http://Holly:8889/PremiseWebService
2015-01-20 20:30:26,538 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opening...
2015-01-20 20:30:26,538 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opening event received
2015-01-20 20:30:26,557 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opened event received
2015-01-20 20:30:26,557 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opened, waiting for clients
2015-01-20 20:30:26,557 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver starting subscription checker timer
2015-01-20 20:30:48,677 [17] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2015-01-20 20:30:48,677 [17] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect - Creating new session to holly
2015-01-20 20:30:53,115 [9] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2015-01-20 20:30:53,115 [9] INFO - [PremiseWebServiceLibLogger] Session already exists. Reutilizing session with holly
2015-01-20 20:30:53,116 [9] DEBUG - [PremiseWebServiceLibLogger] Function GetPremiseConnection called


I am getting this with both firewalls open on ports 8888-8889 and the PremiseMetro settings with just the Proxy Server and Server pointed to my server by name.
 
Any clue what might be happening?
 
It looks like it's calling the web service properly.   Do you see a back arrow on the window?  If so, tap it. 
 
Very strange.  I'll look at my code when I get home, but it's almost acting like it can't find sys://Home.
 
Where the logs stop is where the broker service is trying to connect to the sys://Home object in the Premise hierarchy.  So either the session with Premise itself dropped there or somehow, the sys://Home object is inaccessible (which is highly unlikely unless it's been renamed.  I'm posting a version of the Web Services service with some more logging around the section where I think it's getting stuck.  Please try it when you have a chance.  Don't forget to set your logging level to DEBUG in the LOG4NET file in the installation directory.
 
Give me a few minutes and I'll have the new version posted.
 
Curious:
 

2015-01-22 20:53:16,744 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services OnStart command received. Worker thread starting
2015-01-22 20:53:16,754 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services worker thread started
2015-01-22 20:53:16,770 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver Server method started
2015-01-22 20:53:16,784 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.0.210
2015-01-22 20:53:16,784 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 127.0.0.1
2015-01-22 20:53:16,808 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost created using service URL: net.tcp://Holly:8888/PremiseWebService
2015-01-22 20:53:16,809 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver NetTCPBinding created
2015-01-22 20:53:16,809 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost endpoint added
2015-01-22 20:53:16,809 [7] INFO - [PremiseWebServicesDriverLogger] Starting metadata service on: http://Holly:8889/PremiseWebService
2015-01-22 20:53:16,809 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opening...
2015-01-22 20:53:16,809 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opening event received
2015-01-22 20:53:16,828 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opened event received
2015-01-22 20:53:16,828 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opened, waiting for clients
2015-01-22 20:53:16,828 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver starting subscription checker timer
2015-01-22 20:53:30,063 [8] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2015-01-22 20:53:30,063 [8] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect - Creating new session to holly
2015-01-22 20:53:36,421 [15] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2015-01-22 20:53:36,422 [15] INFO - [PremiseWebServiceLibLogger] Session already exists. Reutilizing session with holly
2015-01-22 20:53:36,422 [15] DEBUG - [PremiseWebServiceLibLogger] Function GetPremiseConnection called
2015-01-22 20:53:36,425 [15] ERROR - [PremiseWebServiceLibLogger] PremiseBroker::Connect - Failed to retrieve sys://Home object: Object reference not set to an instance of an object.

Not finding SYS://Home object.
 
That's the issue.  Do you have your firewall blocking minibroker traffic?  Is Minibroker a registered DLL on the machine running the service (happens automatically when Premise is installed, but you nee to do it manually with regsrv if you are running the service on a non-Premise machine)
 
It's installed on the server itself.  As far as I can tell, minibroker isn't being blocked.  I'm not sure which version of it I have there.  I seem to recall a couple floating around.
 
I've got to put some more debugging code in, but I'm not sure what the issue could be.  This is a very basic function.  I call GetObject("sys://Home") in the service, and it appears to be failing.  Do you happen to have any other minibroker-based apps installed and working?
 
I am using the MiniBrowser with Chuck's JQuery setup.  But I have had other issues over the years of using this installation.  Like I still can't run you UPnP Control point.  I'm thinking about rebuilding soon.  This may accelerate it.  There does seem to be something a bit off on my installation.
 
Back
Top