XBMC minimizes / shrinks on startup (windows 7)
#16
Check the debug log to be sure, but my guess is you have some software using the TCP/IP port XBMC is trying to use. Go into Settings, Network and either disable the options to allow other software to control XBMC, or change the port number.

JR
Reply
#17
ok, thanks, i will try this.

But it can only be Eventghost, but actually it is uninstalled already.
Reply
#18
If you open a command prompt and type (when XBMC isn't running):

Code:
netstat -an | find "TCP" | find "LISTENING"

This will show you all the ports Windows is currently using. For example when I do this I get:

Code:
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
and so on for several more lines

The 0.0.0.0:80 tells me that port 80 is being used, so in XBMC System settings, Network, Services I have to change the Port setting from the default of 80 (I use 81). If I use the command when XBMC is running I get:

Code:
TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
TCP    0.0.0.0:81             0.0.0.0:0              LISTENING
TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
etc

showing that XBMC is using port 81.

JR
Reply
#19
Code:
Aktive Verbindungen

  Proto  Lokale Adresse         Remoteadresse          Status
  TCP    0.0.0.0:135            0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:443            0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:445            0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:554            0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:912            0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:2869           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:3389           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:3483           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:5938           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:9000           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:9090           0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:10243          0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:49152          0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:49153          0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:49154          0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:49155          0.0.0.0:0              ABHÖREN
  TCP    0.0.0.0:49177          0.0.0.0:0              ABHÖREN
  TCP    127.0.0.1:5939         0.0.0.0:0              ABHÖREN
  TCP    127.0.0.1:5939         127.0.0.1:49179        HERGESTELLT
  TCP    127.0.0.1:5939         127.0.0.1:49334        HERGESTELLT
  TCP    127.0.0.1:49157        127.0.0.1:49158        HERGESTELLT
  TCP    127.0.0.1:49158        127.0.0.1:49157        HERGESTELLT
  TCP    127.0.0.1:49159        127.0.0.1:49160        HERGESTELLT
  TCP    127.0.0.1:49160        127.0.0.1:49159        HERGESTELLT
  TCP    127.0.0.1:49179        127.0.0.1:5939         HERGESTELLT
  TCP    127.0.0.1:49332        127.0.0.1:49333        HERGESTELLT
  TCP    127.0.0.1:49333        127.0.0.1:49332        HERGESTELLT
  TCP    127.0.0.1:49334        127.0.0.1:5939         HERGESTELLT
...
  TCP    [::]:135               [::]:0                 ABHÖREN
  TCP    [::]:445               [::]:0                 ABHÖREN
  TCP    [::]:554               [::]:0                 ABHÖREN
  TCP    [::]:2869              [::]:0                 ABHÖREN
  TCP    [::]:3389              [::]:0                 ABHÖREN
  TCP    [::]:10243             [::]:0                 ABHÖREN
  TCP    [::]:49152             [::]:0                 ABHÖREN
  TCP    [::]:49153             [::]:0                 ABHÖREN
  TCP    [::]:49154             [::]:0                 ABHÖREN
  TCP    [::]:49155             [::]:0                 ABHÖREN
  TCP    [::]:49177             [::]:0                 ABHÖREN

if XBMC is not running, i get this.
so no port 80 is used actually?
Reply
#20
We need to see a debug log.

Enable debug logging from System settings, System, Debugging, and restart XBMC.

A quick way to open the debug log is to press Windows-R and in the Run dialog type:

"%appdata%\xbmc\xbmc.log"

(including the quotes). Click OK and the log should open in Notepad. Copy and paste the log into pastebin.com and post the link it gives you here.

JR
Reply
#21
here is the log

http://pastebin.com/ryD0k3LB

and webserver issue is gone (i can connect to the xwmm webserver...),
only
"XBMC Remote communication server failed to start."
i still get?

thanks!!
Reply
#22
Ah, it's the JSON server and it's trying to use port 9090. If you look at the output you got from netstat you'll see in includes:

Code:
TCP    0.0.0.0:9090           0.0.0.0:0              ABHÖREN

so you have some app already listening on 9090.

If you go into System settings, Network, Services and disable the setting "Allow programs on this system to control XBMC" you should find the error goes away, though to be fair this is addressing the symptom not the disease. It can be hard to work out what is using a port like 9090, especially if you're a non-nerd :-) If you open http://live.sysinternals.com/tcpview.exe in Internet Explorer then choose Run when prompted, this is an app that will tell you what process is using what port. Look in the "Local port" column, or even better click that column heading to sort by the port and make it easier to find 9090. Note the file name shown in the "Process" column, and that's your villain.

JR
Reply
#23
oh thank you, will try this tonight.

I think its the squeezebox server software that uses port 9090 :-)
Reply
#24
yep, its the squeezebox server! :-) thanks!
Reply
#25
I have this same problem, only way I'm able to fix it on win7 64 home premium is to get xbmc to put the computer to sleep, and then turn it back on where I left it.

If anyone has an idea can they post it up.
Current Setup:
[T.V] 55" Bravia HX820 3D [Reciever] Sony 7.1 Surrond 3D
RPi B+ | Openelec | OC@1000MHz

In Process
[OS] Win 7 64Bit HP [CPU] AMD Athlon™ 64 X2 4800+ 2.5GHz [MOBO] nVIDIA Quadro NVS 210S [RAM] 2x2GB DDR2 Kingston [GPU] Radeon HD6450 1GB DDR3 [HDD] 1TB WD SATA [Audio] Radeon HD6450 (HDMI Out)
Reply
#26
strykr192 Wrote:I have this same problem

Please start a new thread with full details including a debug log.

JR
Reply
#27
I have the same problem too. Even the "-d 10" switch doesn't help.

Has anyone succeeded?
Reply
#28
pipps Wrote:Has anyone succeeded?

Dozens of results can easily be found searching this forum, the vast majority with successful resolution. This thread alone holds several proven solutions. It depends on your setup as to what is causing the problem. Imon, squeezebox, Catalyst, and several other programs are notorious for causing this problem.

To start with, you don't have to use 10 as the default delay. You can make it 20, or 30, or 4532. Whatever it takes to stall XBMC long enough for the other programs to finish their startup. If it's Catalyst, often times delays won't help, only disabling catalyst will do the trick. Also, I know that the -d switch stopped functioning for a while on some of the nightlies, no clue if it is working again or not. Use the task scheduler and/or a batch script instead, as they will always work no matter what is changed with XBMC.

If you want to definitively isolate the offending focus stealing program, you can hit start and in the run box type msconfig and hit enter. On the startup tab, disable everything other than XBMC. Restart, you should not lose focus. Assuming you don't lose focus, which you shouldn't, start re-enabling all of your start up items ONE AT A TIME, reboot and see if you lose focus. Keep doing this until you reboot and lose focus, then you have your problem software identified.

At that point, you can either disable the program causing the problem, go to that softwares support site and see if they have a solution, or experiment to determine exactly how long you need to wait before XBMC starts to avoid losing focus.


A brief warning about msconfig; If you do not know what you are doing, do not mess with anything other than the items on your startup tab. You can easily wreck your machine with this tool and should you should not experiment with this tool unless you know what you are doing. Disabling everything in the startup tab will not do any harm to your machine, however you should remember to go back and enable all of the things you want to start with the computer when you are finished with your troubleshooting.
Reply
#29
Thanks for the great reply. I look forward to testing my startup processes!
Reply
#30
I too have this problem. I will try to disable Catalyst but I thought that was needed for the display. Will give it a try.
Reply

Logout Mark Read Team Forum Stats Members Help
XBMC minimizes / shrinks on startup (windows 7)0