Jump to content


Cannot create the Personal Server


  • Please log in to reply
15 replies to this topic

#1 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 22 February 2019 - 01:50 PM

Hi,
I have Helix P4V/NTX64/2018.4/1753667 and try to create a personal server. P4v.exe --> Personal Server --> Initialize New Personal Server --> User Name, Location --> Unicode Support  --> Case Sensitive --> Unicode (UTF-8) (it may be any other indeed). When I press Create button I get the following errors:
Connect to server failed; check $P4PORT.
Unknown P4CHARSET auto.

The OS is Windows 2016 server, p4v was installed with its Windows installer "as is" and the environment has no $P4XXX variables set. Does Perforce Personal Server work at all?

P.S. I know that neither Perforce web site nor this forum work with the MS LTSB OSes. But what about the Perforce server?..

#2 P4Jen

P4Jen

    Advanced Member

  • Staff Moderators
  • 147 posts

Posted 25 February 2019 - 06:06 PM

Hi,

I would like to rule out an issue with P4V, so please try creating a DVCS server on the command-line, using the command:
  p4 init -xi

This will create a server with unicode support, under the directory location you are at when you run the
command.

Also let us know which version of P4D is on the machine where you are trying to create this personal server.

You can find this out by running:
  p4d -V

from the command prompt.

If you have a valid support contract, you may wish to contact technical support for assistance.

Best,
Jen.




#3 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 26 February 2019 - 01:20 AM

> I would like to rule out an issue with P4V, so please try creating a DVCS
> server on the command-line, using the command:
>  p4 init –xi
I cannot just do it because your installer places the p4d into f:\Perforce\DVCS, but p4.exe and system path is placed/set to f:\Perforce. So it will not work. But I have copied the p4d.exe to f:\Perforce. So,
p4 init -xi
I get the following:
No available server to discover configuration, needs flags to
specify case sensitivity and Unicode settings:   
p4 init [-C0|-C1]   (case-sensitive or case-insensitive)
p4 init [-xi|-n]    (with Unicode support or without it)
Note, it is important to initialize with the same case sensitivity
and Unicode settings as the server you wish to push/fetch from.  
For more information, run: 'p4 help init'.   

Ok, it looks like p4 init requires case controlling flag. At least on Windows. Ok, let us add it:
p4 init -xi -C0
Connect to server failed; check $P4PORT.
Unknown P4CHARSET auto.
So it is the same error I get with p4v. The only difference it knows about the location of the p4d executable.
> Also let us know which version of P4D is on the machine where
> you are trying to create this personal server.
This is the version that comes with Helix P4V/NTX64/2018.4/1753667. p4d -V reads
Perforce - The Fast Software Configuration Management System.  
Copyright 1995-2019 Perforce Software.  All rights reserved.  
Portions copyright 1991-2005 Compuware Corporation.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)   
Version of OpenSSL Libraries: OpenSSL 1.0.2q  20 Nov 2018   
See 'p4 help [ -l ] legal' for additional license information on
these licenses and others.
Rev. P4D/NTX64/2018.2/1751184 (2019/01/21).
License: none   
> If you have a valid support contract, you may wish to contact
> technical support for assistance.
No, I do not, I do not have a support. This forum only.

#4 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 26 February 2019 - 01:37 AM

There is a chance that I have replaced the p4d.exe with the latest version from your ftp. But I assure you that the original p4d.exe from Helix P4V/NTX64/2018.4/1753667 installation gave the same results -- of course I have given a try to the command line tools before addressing here.

#5 P4Jen

P4Jen

    Advanced Member

  • Staff Moderators
  • 147 posts

Posted 28 February 2019 - 06:13 PM

Hi Michael,

Thanks for giving that a try.

I would like to verify what codepage is being used, so send the output of:
  chcp

I have had a look through our bug tracking system, and so far haven't found anything that exactly matches your issue.

I also saw that you created another thread linked to this one.

Please use this thread when replying, as it's easier if the information is all in one place.

Best,
Jen.


#6 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 01 March 2019 - 05:57 PM

Hi. Sorry if the parallel thread violates the Perforce policy. I just see it may be not a p4v issue and the General forum may appear to be more alive.
chcp (I have never heard of it) reads:
Active code page: 866

#7 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 976 posts

Posted 04 March 2019 - 11:13 PM

Just to double-check, is your p4 client (p4 -V) also at version 2018.2?  IIRC, the client itself is supposed to translate a charset of "auto" before sending it to the server, so if it's failing to do that it could be that the client out of date.

That aside, according to the relnotes, Windows codepage 866 isn't one of the ones that the client recognizes anyway (it SHOULD be giving you a better error, but whatever).  So you probably want to set it manually to one of the options listed in the relnotes: https://www.perforce...r/i18nnotes.txt

(That or disable Unicode mode and just use ASCII for everything...)

#8 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 04 March 2019 - 11:54 PM

p4 -V reads
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2019 Perforce Software.  All rights reserved.
This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit (http://www.openssl.org/)
Version of OpenSSL Libraries: OpenSSL 1.0.2q  20 Nov 2018
See 'p4 help [ -l ] legal' for additional license information on
these licenses and others.
Extensions/scripting support built-in.
Parallel sync threading built-in.
Rev. P4/NTX64/2018.2/1751184 (2019/01/21).

I do not use p4, I use p4v and I have tried many language settings from it’s dropdown list – all in vain. But Ok, I run
p4 set -s P4CHARSET=cp1251
then p4 init -xi -C0 as far as I need the Unicode server to be able to promote changed to the Unicode server. I geet
Connect to server failed; check $P4PORT.
Unknown P4CHARSET auto.

If I run p4 set -s P4CHARSET=cp1251 again, I get
Character set must be one of:
none, auto, utf8, utf8-bom, iso8859-1, shiftjis, eucjp, iso8859-15,
iso8859-5, macosroman, winansi, koi8-r, cp949, cp1251,
utf16, utf16-nobom, utf16le, utf16le-bom, utf16be,
utf16be-bom, utf32, utf32-nobom, utf32le, utf32le-bom, utf32be,
cp936, cp950, cp850, cp858, cp1253, iso8859-7, utf32be-bom,
cp852, cp1250, or iso8859-2.
Check P4CHARSET and your '-C' option.

I have to clean my PersonalServerDirectory (I execute all p4 commands in it) to restore the p4 functionality. It does not work anymore with the error message above. Really strange. Ok. Let it be a totally useless for me personal server without any Unicode.
Clean the PersonalServerDirectory for p4 to be able to work again.
p4 set -s P4CHARSET=cp1251
p4 init -C0
p4 hangs for a really long time. Then I see
No available server to discover configuration, needs flags to
specify case sensitivity and Unicode settings:
p4 init [-C0|-C1]   (case-sensitive or case-insensitive)
p4 init [-xi|-n]    (with Unicode support or without it)
Note, it is important to initialize with the same case sensitivity
and Unicode settings as the server you wish to push/fetch from.
For more information, run: 'p4 help init'.

#9 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 04 March 2019 - 11:58 PM

PersonalServerDirectory is filled with some stuff from unsuccessful p4 init -xi -C0 command. It looks like p4 tries to read the configuration from it and gets stuck on it.

#10 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 976 posts

Posted 04 March 2019 - 11:59 PM

What if you just go to an empty directory and do:

p4 -C cp1251 init -C0 -xi

?

#11 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 05 March 2019 - 12:00 AM

Sorry for strange formatting. I have found a workaround for IE11 and this forum but it half works.

#12 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 05 March 2019 - 12:05 AM

It worked!!! Thank you. And p4v was able to open it. Thank you a lot!
But, please, note that I have had to copy p4d next to p4 manually.

#13 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 05 March 2019 - 12:10 AM

I have really tried this before but p4 failed on the garbage in PersonalServerDirectory. And I have thought that -C just was not supported in init command. It took me a time to invent PersonalServerDirectory cleaning.

#14 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 06 March 2019 - 04:36 AM

Well, I will not even ask additional questions. This is early morning already and I still cannot make the Personal Server to work. But I know a lot of methods to make p4v to crash while trying to work with the Personal Server and at least one method how to almost kill my 8 processors VMWare test machine with p4d zombies that eat the whole CPU time.
I probably shall wait for a more stable release of the feature.

#15 MichaelK

MichaelK

    Advanced Member

  • Members
  • PipPipPip
  • 51 posts

Posted 29 November 2019 - 08:30 AM

Hello. Can anybody with the valid Perforce support address them with the issue? Does the Perforce personal server work at all on Windows?
And anybody who use the Perforce personal server regularly on Windows, could you, please, drop a line here about your experience? I still believe I am the only Perforce Windows user in the world but there is a chance that I just press the wrong buttons.
Thank you in advance.

#16 Sambwise

Sambwise

    Advanced Member

  • Members
  • PipPipPip
  • 976 posts

Posted 30 November 2019 - 11:47 PM

I haven't ever had any problems using a personal server from the command line (by running "p4 init"), but can't speak to the experience of using it from P4V.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users