7 replies to this topic

[luken]

I loaded proiv 55r333 on WIndows Server 2003 Standard Edition. When trying to start the service it hangs. This is a clean installation no previous version on the machine.

[Joseph Bove]

Luken,

Complete shot in the dark, but look for firewall software that is blocking port 23. Try disabling all firewall software and then starting the ProIV service.

Good luck,

Joseph

[luken]

Hi Joseph,

Thanks for your reply, I will try your suggestion. I have however picked up some event viewer errors as follows:

Sockwait select[] failed last win32 error 10022 / winsock error 10022 invalid argument.

Socklisten : bind socket failed last win32 error 10013 / winsock error 10013: access denied.

I have no idea if this could very well be a firewall problem.

[Bill Loven]

Luken

Do you have SP2 applied to your Windows 2003 Server install?

We have all but one installation running on Windows Server 2003 with no problems and do not have SP2 installed.

With all that I read about SP2, it breaks more than it fixes.

Bill.

[Sindre Solem]

Luken

Download TCPview from sysinternals.com and check if anything is listening on the telnet port (23). It could be the Windows telnet server, of course.

-Sindre

[luken]

Thanks for all your replies.

I have got the service to start by stopping the telnet service, but cannot start the telnet service one the proiv service has started.
To get one to log into proiv remotely I need the telnet service. How do I get arround this problem.

[luken]

[B]I AM A LIAR. IT DOES CONNECT REMOTELY. FORGET THE LAST POST.

[tom braider]

Yes I had this message "Invalid Argument" and the reason for me was I had omitted the 'Directory in Which PROIV Kernel is Installed' path. This is located in the Host tab in View, Options pull down menu.

Once this was supplied it worked fine.