Assuming you are running the latest version (check the downloads section, I posted an update awhile back), there is either a permissions problem on the directory holding the service executable or the minibroker.dll file is not registered (UNLIKELY). LOCAL SYSTEM must have full control of the executable's directory. You also need to disable DEP for all but critical windows files.
Premise PremiseMetro - a ModernUI interface for Premise
- Thread starter georgejm
- Start date
Motorola Premise
samgreco
Active Member
I re-downloaded everything. Re-installed everything. I still get exactly the same error/issues.
Config error and no log files showing up.
I do have DEP set to on for ONLY essential Windows stuff. It looks as though your service runs under the system account and it has permissions to the Premise Web Services folder. I'm sure MiniBroker is registered. But I tried manually registering it just to be sure.
So now I am at a complete loss.
Config error and no log files showing up.
I do have DEP set to on for ONLY essential Windows stuff. It looks as though your service runs under the system account and it has permissions to the Premise Web Services folder. I'm sure MiniBroker is registered. But I tried manually registering it just to be sure.
So now I am at a complete loss.
samgreco
Active Member
In the C:\Program Files (x86)\GeorgeCo Professional Services\Premise Web Services directory are just the 4 files I mentioned earlier.
I installed Web Services on my Windows 8 workstation and stopped the service on the server. Tried to run Premise Metro and got the same thing. And no log files in the directory on the workstation either.
I installed Web Services on my Windows 8 workstation and stopped the service on the server. Tried to run Premise Metro and got the same thing. And no log files in the directory on the workstation either.
Okay. It looks like the latest version didn't upload when I did the update back in June. I switched to the Advanced Uploader and that appeared to correctly upload the zip file. Try it again, use the larger zip file (both are still there in the downloads section).
Sorry about that, I usually do a check install after I upload stuff to the forum. Didn't do that this time.
Sorry about that, I usually do a check install after I upload stuff to the forum. Didn't do that this time.
samgreco
Active Member
First: Never a need to apologize 
Well, a step forward. I have installed the updated version onto the Premise server. I now have the Log folder and a file in it. Unfortunately, the file is 0 bytes. I am getting the same error.
I changed the services login settings to allow desktop interaction just for yucks. Still no love. But it did create a new log file. But it is also 0 bytes.
Well, a step forward. I have installed the updated version onto the Premise server. I now have the Log folder and a file in it. Unfortunately, the file is 0 bytes. I am getting the same error.
I changed the services login settings to allow desktop interaction just for yucks. Still no love. But it did create a new log file. But it is also 0 bytes.
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<log4net>
<appender name="PremiseWebServicesAppender" type="log4net.Appender.RollingFileAppender">
<file value="logs\PremiseWebServices.log" />
<appendToFile value="false" />
<rollingStyle value="Date" />
<DatePattern value="_yy-MM-dd.lo\g"/>
<maxSizeRollBackups value="3" />
<maximumFileSize value="100KB" />
<staticLogFileName value="false" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%thread] %-5level -
[%logger] %message%newline" />
</layout>
</appender>
<logger name="PremiseWebServiceLibLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServiceSVCLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServicesDriverLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServiceStubLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
</log4net>
</configuration>
Getting closer. There should be a file in the executables directory that is called PremiseWebServiceLib.dll.log4net. When you open it with notepad it should look something like the above. Everywhere you see "WARN", make it "ALL". That should tell us if the UI is even talking to the server.
<configuration>
<log4net>
<appender name="PremiseWebServicesAppender" type="log4net.Appender.RollingFileAppender">
<file value="logs\PremiseWebServices.log" />
<appendToFile value="false" />
<rollingStyle value="Date" />
<DatePattern value="_yy-MM-dd.lo\g"/>
<maxSizeRollBackups value="3" />
<maximumFileSize value="100KB" />
<staticLogFileName value="false" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%thread] %-5level -
[%logger] %message%newline" />
</layout>
</appender>
<logger name="PremiseWebServiceLibLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServiceSVCLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServicesDriverLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
<logger name="PremiseWebServiceStubLogger">
<level value="Warn" />
<appender-ref ref="PremiseWebServicesAppender" />
</logger>
</log4net>
</configuration>
Getting closer. There should be a file in the executables directory that is called PremiseWebServiceLib.dll.log4net. When you open it with notepad it should look something like the above. Everywhere you see "WARN", make it "ALL". That should tell us if the UI is even talking to the server.
samgreco
Active Member
Here's what I've got:
Code:
2014-08-29 13:59:08,239 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services OnStart command received. Worker thread starting
2014-08-29 13:59:08,247 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services worker thread started
2014-08-29 13:59:08,257 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver Server method started
2014-08-29 13:59:08,297 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.0.210
2014-08-29 13:59:08,297 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.197.1
2014-08-29 13:59:08,297 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.226.1
2014-08-29 13:59:08,297 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 127.0.0.1
2014-08-29 13:59:08,321 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost created using service URL: net.tcp://Holly:8888/PremiseWebService
2014-08-29 13:59:08,322 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver NetTCPBinding created
2014-08-29 13:59:08,322 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost endpoint added
2014-08-29 13:59:08,322 [7] INFO - [PremiseWebServicesDriverLogger] Starting metadata service on: http://Holly:8889/PremiseWebService
2014-08-29 13:59:08,322 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opening...
2014-08-29 13:59:08,322 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opening event received
2014-08-29 13:59:08,340 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opened event received
2014-08-29 13:59:08,340 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opened, waiting for clientsBased on the log, the client isn't talking to the server. If you are running firewall on either the client or the server, you need to enable port 8888 for TCP. It also looks like you have three networks on your server. I'm curious which path the client takes to the server. Can you successfully ping the server from the client by name?
samgreco
Active Member
Curious. I really hadn't noticed that, but I did see it somewhere along the way. Not sure where the "extra" ip addresses are coming from.
If I ping my server by name, I get the first IP Address - 192.168.0.210. But I just looked at the default website properties in SYS Builder, and sure enough, it shows 192.168.226.1. I haven't found the 3rd anywhere. Any idea why the default webserver would show a different address and where it can be changed. Because I can't in the properties block.
But I cannot change the default website properties.
But I just opened up the port 8888 on the server and the log has filled up. It was obviously connecting as I can see a list of room, etc being called and such. I did get a "PremiseServerError" on opening of the PremiseMetro UI after a very long spinning progress wheel.
I cleaned up some unused modules and such, now I get that error instantly. And I don't see the list of rooms connecting. Back to a simple log, with almost instant error.
If I ping my server by name, I get the first IP Address - 192.168.0.210. But I just looked at the default website properties in SYS Builder, and sure enough, it shows 192.168.226.1. I haven't found the 3rd anywhere. Any idea why the default webserver would show a different address and where it can be changed. Because I can't in the properties block.
But I cannot change the default website properties.
But I just opened up the port 8888 on the server and the log has filled up. It was obviously connecting as I can see a list of room, etc being called and such. I did get a "PremiseServerError" on opening of the PremiseMetro UI after a very long spinning progress wheel.
I cleaned up some unused modules and such, now I get that error instantly. And I don't see the list of rooms connecting. Back to a simple log, with almost instant error.
Code:
2014-09-02 18:05:21,912 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services OnStart command received. Worker thread starting
2014-09-02 18:05:21,922 [5] INFO - [PremiseWebServiceSVCLogger] Premise Web Services worker thread started
2014-09-02 18:05:21,938 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver Server method started
2014-09-02 18:05:21,979 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.0.210
2014-09-02 18:05:21,979 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.197.1
2014-09-02 18:05:21,979 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 192.168.226.1
2014-09-02 18:05:21,980 [7] DEBUG - [PremiseWebServicesDriverLogger] Found IP Address: 127.0.0.1
2014-09-02 18:05:22,005 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost created using service URL: net.tcp://Holly:8888/PremiseWebService
2014-09-02 18:05:22,007 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver NetTCPBinding created
2014-09-02 18:05:22,007 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost endpoint added
2014-09-02 18:05:22,007 [7] INFO - [PremiseWebServicesDriverLogger] Starting metadata service on: http://Holly:8889/PremiseWebService
2014-09-02 18:05:22,007 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opening...
2014-09-02 18:05:22,007 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opening event received
2014-09-02 18:05:22,024 [7] DEBUG - [PremiseWebServicesDriverLogger] Service opened event received
2014-09-02 18:05:22,024 [7] INFO - [PremiseWebServicesDriverLogger] WebServicesDriver ServiceHost opened, waiting for clients
2014-09-02 18:05:32,657 [12] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2014-09-02 18:05:32,657 [12] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect - Creating new session to holly
2014-09-02 18:05:45,746 [9] INFO - [PremiseWebServiceLibLogger] PremiseBroker::Connect called for holly with Username:
2014-09-02 18:05:45,747 [9] INFO - [PremiseWebServiceLibLogger] Session already exists. Reutilizing session with holly
2014-09-02 18:05:45,747 [9] DEBUG - [PremiseWebServiceLibLogger] Function GetPremiseConnection calledSimilar threads
