hi i am trying to link source control to perforce in redgate tool for sql server management studio but it throws error like
Command:
P4 -c C:\myworkspace_name-LT_2632\webteam\SANDBOXES\sandboxname -s sync "C:\myworkspace_name-LT_2632..."
Output:
error: Client 'C:\myworkspace_name-LT_2632\webteam\SANDBOXES\sandboxname' unknown - use 'client' command to create it.
exit: 1
The -c argument to p4 specifies the name of a client workspace. As the error message indicates, you are telling it to run the sync command in a client named 'C:\myworkspace_name-LT_2632\webteam\SANDBOXES\sandboxname'. From your comment on the original question, I think you need to change myworkspace in the example to the name of the client workspace that maps the path you listed.
Related
Recently I am working on upgrading my opensips version manually from 2.2 to 3.3.
Upgradation is done from my side but in old opensips(2.2) I was able to show registered user(SIP) using opensipsctl ul show command but in new version 3.3 opensipsctl is deprecated(I guess not sure).
So I am trying to get details using opensips-cli but I didn't find out correct command for show register and show dump list, I try to follow below link but did not find correct command.
https://www.opensips.org/Documentation/Interface-CoreMI-3-0
Also, my opensips-cli -x command not working giving the below error. (mi_fifo module loaded correctly)
# opensips-cli -o output_type=yaml -x mi uptime
ERROR: cannot access fifo file /tmp/opensips_fifo: [Errno 13] Permission denied: '/tmp/opensips_fifo'
ERROR: starting with Linux kernel 4.19, processes can no longer read from FIFO files
ERROR: that are saved in directories with sticky bits (such as /tmp)
ERROR: and are not owned by the same user the process runs with.
ERROR: To fix this, either store the file in a non-sticky bit directory (such as /var/run/opensips),
ERROR: or disable fifo file protection using 'sysctl fs.protected_fifos=0' (NOT RECOMMENDED)
/tmp/opensips_fifo file also created correctly.
# ls -l /tmp/opensips_fifo
prw-rw-rw- 1 opensips opensips 0 Dec 29 06:52 /tmp/opensips_fifo
Using opensips-cli command I am able to create database and add table but not able to perform -x command.
Can anyone help me to find out a command for show register and show dump list also any suggestion related -x command not working on opensips-cli.
I had a similar error and i found the following:
if you state in the opensips-cli.cfg file that the fifo_file is located at /tmp/opensips_fifo, it will produce this error, try changing this setting to /var/run/opensips/opensips_fifo
Whenver I try to run p4 command p4 change -o or pythonically p4.fetch_change()
I get this error message !
[Error]: "Client 'hostname' unknown - use 'client' command to create it."
Does anyone know why am I getting this ?
You don't have a client workspace defined. The changelist spec you get from p4 change -o is the spec for the default pending changelist associated with your current client. If you don't have a client, you'll get that error. You'll see the same behavior for any other command that depends on a client spec (which is most of them).
As the error says, use p4 client to define a new client specification. If you already have a client for hostname, use p4 set to set P4CLIENT to the name of that client.
I'm using RS.exe to migrate from a sharepoint-integrated SSRS server to a standalone SSRS server. When I run the command I think SHOULD work, I get an error related to a missing SiteURL parameter. I want to copy all contents from the source SSRS box to the destination, so my understanding is that the defaults should be acceptable. Documentation for this migration path seems thin. I'd appreciate help in figuring out how to get this done.
Below are the command and error text:
c:\IT>rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SPssrs/ReportServer -v ts="http://reporting/ReportServer"
Retrieve and report the list of items that will be migrated. You can cancel the script after step 1 if you do not want to start the actual migration.
Retrieving schedules:
Unhandled exception:
The value for parameter 'SiteUrl' is not specified. It is either missing from the function call, or it is set to null.
Try
rs.exe -i ssrs_migration.rss -e Mgmt2010 -s http://SPssrs/_vti_bin/ReportServer -v ts http://reporting/reportserver
Suddenly, when I run p4 info in terminal, I notice that the client root is not set (not sure why it got unset all of a sudden. Following is the output which shows "client unknown" in place of client root. What is the command through which I can set the same? I have tried p4 client and p4 set but may be, with wrong syntaxes.
BANL121b92746:Applications bagarwal2$ p4 info
User name: bagarwal2
Client name: BANL121b92746
Client host: BANL121b92746.local
Client unknown.
Current directory: /Applications
And is the value of this client root be the same as "Workspace Root" set in my P4V client under Connections->Edit Workspace . My P4V client is working perfectly. I found this problem with p4 info when my Intellij IDEA started showing connection problems in P4. On testing the connection in IDEA, below is the error screenshot, which is same as when I do p4 info in terminal.
Regarding my p4settings.txt config, below are the configs which were working for months till now:
P4HOST=<hidden hostname>:2500
P4CLIENT=bagarwal2_BANL121b92746_trunk
P4USER=bagarwal2
P4POST=<hidden hostname>:2500
My P4V connection (which works all fine), uses the same details/config which are mentioned above, still I find this problem in terminal and hence in Intellij IDEA.
Try p4 set p4client=my_client.
This stores your preferred client in the registry. There are other ways to set your client, with different precedence and scope:
environment variables (potentially different per process)
P4CONFIG files (potentially different per filesystem location)
command-line options (potentially different for every invocation of p4.exe)
but for simplicity, using p4 set is all you should need.
BTW, P4V uses its own setting (there's a dialog that comes up by default when you start P4V).
It looks like your p4settings.txt config file isn't being used; otherwise the client name returned by "p4 info" would match the P4CLIENT value in the config file. Run:
p4 set P4CONFIG=p4settings.txt
and make sure that when you run "p4 info" you're doing it from a directory underneath ~/dev/trunk. (Your "p4 info" output in the question shows your current directory as /Applications, so that might explain the problem on its own -- just do "cd ~/dev/trunk" and try again.)
The "client unknown" error suggests that maybe your client spec got deleted (this is assuming you're connecting to the same server and using the same client name you were successfully using before). If that's what happened you can create a new one with the same name by running:
p4 client
UNIX: bash, ksh, sh,
P4CLIENT=value ; export P4CLIENT
UNIX: csh
setenv P4CLIENT value
Mac OS X (bash)
P4CLIENT=value ; export P4CLIENT
Windows
p4 set P4CLIENT=value
Windows administrators running Helix Server as a service can set variables for use by a specific service with p4 set -S svcnamevar=value, or set variables for all users on the local machine with p4 set -s var=value.
More details here:
https://www.perforce.com/manuals/cmdref/Content/CmdRef/envars.html
SET P4PORT in the environment variable.
then when you try P4 info
client unknown error will be gone & it will show the p4root value which is set in perforce.
It worked for me.
I ran into this issue, and come to find out the perforce registry keys under Computer\HKEY_CURRENT_USER\SOFTWARE\Perforce\Environment are case sensitive! Somehow, someway, the P4CLIENT key was set to p4client. Setting it to upper case and then running p4 client command solved the issue for me.
Given:
- Installed 64bit Windows perforce plugin
- My workspace root: "c:\source"
- Set "Add workspace root" from plugin preferences
- Right click on file in "c:\source\project1" select check out
- No status icons visible (checked in/out/, out of date, etc,)
Error:
Client '' unknown - use 'client' command to create it.
Set environmental variable P4CLIENT to your workspace name. Your workspace name is stored in p4 visual client under Connection->Edit Current Workspace
You need to create the client by running p4 client on the command line or using P4V.
I had the same problem. Using
set P4CLIENT=my_workspace_name
in the terminal and then using p4 commnd has worked for me.
In my case the ~/.p4enviro config file was using an outdated value for the P4CLIENT. I updated the value to the correct name of my current workspace and it fixed the problem.