Our Perforce configuration has a commit server and 2 edge server.
There is no license in commit sever. We are using 20 free copies and use all license
Btw, we purchase 30 copies of Perforce license in one of edge server and set it up.
But in edge server user cannot create a client in edge sever.
Edge sever admin check "p4 license -u"
It shows 10 copies user available and clients only.
Why it shows usage of commit server users?How to separate this from commit server free license?
30 copies of license has to be used only edge server users.
Related
My source code server has been infected ransomware and when I want connect to the VisualSVN via Tortoise SVN the following message is displayed :
VisualSVN runs without any problems and Everything(All users, Repos, Branches, Trunks and and so on) is displayed in the VisualSVN server and I can even create a new Repo But I can not connect to it via Tortoise SVN.
This problem continues even after VisualSVN service restarted.
Is there a solution to this problem?
The error tells that the access to the repositories is forbidden. I guess that the virus you caught made modifications to user access rules lists or made them unavailable.
has been infected ransomware
Repair your server or restore the data from backup. And don't forget to ensure that this will never happen in future.
We have introduced a Watch component in our iOS application. If a user launches the app on the Apple Watch, they will be able to see the timing for the next prayer, and the countdown to it, based on their current location.
The user should be able to view this information on the Watch even if the app on the phone is not launched. For this purpose, we need to use Background Location, to ensure we have the user’s current location at all times. The prayer timings are dependent on the user’s location.
Upon submitting this app on the Appstore, our application got rejected for the following reason:
Upon further review we found your application features do not require persistent location. Apps that declare support for location in the UIBackgroundModes key in your Info.plist file must have features that require persistent location.
Please can you suggest me how can I fetch the user’s current location for Watch application when the iOS app is in the background without using UIBackgroundModes key for location services.
I have finally got around to upgrading my perforce server to 2014.
I had a single user Admin Licence, but didn't pay yearly upgrade as I though new free licence would suit me - 20 clients. I just removed the old licence file.
I didn't realise I had 29 clients.
I get this error message
C:\Program Files\Perforce\NewServer>p4d
Perforce server error:
Unlicensed server cannot start while over user/client quota.
Try deleting old clients with 'client -d'.
License count: 29 clients used of 20 licensed.
Is there a way I can select 29 clients to delete? obviously p4 client command won't connect as the server isnt running. Can I run that command against p4d or something similar?
I will contact perforce support on Monday, but wondered if there was anything I could do myself.
We just got hit by this. In the end we issued a
"p4d -n -p 1666"
which put us into maintenance mode. We could then delete client specs. After deleting a few we could start the server again.
I don't know if there is a solution to what I wanted to do, but this is how i solved it.
I had created a full backup of my perforce directory before upgrade.
Unzip backup
Open 'cmd' in backup dir
run p4dfrom commandline, starting the perforce server
connect with normal p4v client
Delete all the additional clients
Shut down p4d window to kill perforce instance
Create Checkpoint
Delete db.* files from real folder
Restore newly created checkpoint to real folder.
All working now.
I have a site when I tried to apply local staging it's worked fine,but we I tried to connect it through remote server it's not working giving error connection can't be established.Does any one tried it?
This is the configuration with the error message:
This blog post (disclaimer: my own) explains how to do it with https - you can omit long parts of it if you don't want encryption. It also covers 6.0, but the general principle is still the same.
You want to pay special attention to the paragraph Allow access to webservices in that article and check if your publishing server (the "stage") has access to the live server. In general, if this is not on localhost, it requires configuration as mentioned in that article.
As you indicate that you can't connect to your production server from your staging server, please check by opening a browser, running on the staging server and connect it to the production server - go to http://production-server-name:8080/api/axis and validate that you can connect (note: You get the authoritative result for this test only when not accessing localhost as the production system: Do run the browser on the staging system!) - with this test you can eliminate the first chance of your remote system being disallowed. Once this succeeds, you'll need credentials for the production server to be entered on the staging server - the account that you use needs to have permissions to change all the data it needs to change when publishing content (and pages etc.)
The error message you give in the added screenshot can appear when the current user on staging does not have access to the production system (with the credentials used) - verify that you have the same user account that you are using on your staging system (the one that gets the error message from the screenshot) in your production system. Synchronize the passwords of the two.
I your comment you give the information that you're using different version for the staging and the production environment - I don't expect that to work, so this might be the root cause. Test with both systems at the same version.
A couple important points to keep in mind with remote publishing:
If you're not on LDAP (or you have different LDAPs for different environments), you should validate that your user account is exactly the same in both source and target environments. So, if you're on the QA site and you want to remote publish to production, your screen name, email address, and password should all be the same.
Email address is uber important. Depending on which distribution (version) of Liferay you are on, the remote publish code uses your email address to irrespective of whether or not you have portal-ext.properties configured to use screenname.
You should have the Administrator role in on both sides. It may not be required in every scenario, but giving that role out to users that do remote publishing has saved me time and effort debugging why someone's remote publish didn't work. Debugging this process takes a very long time.
If remote publishing is causing you problems (and it probably is or you wouldn't be here), try doing lar file exports / imports. This is important since remote publish failures are not exactly helpful in telling you what failed, they just tell you then failed. Surprisingly, there are often problems in the export process and you can sometimes pinpoint some bad documents or a funky development thing you did using Global scope and portlet preferences that caused your RP to fail. I generally use this order in this situation a) documents and media [exclude thumbnails or your lar file will likely double in size, also exclude ranks if you're not using them] from the wrench icon in the control panel b) web content from the wrench icon in the control panel c) public pages [include data > web content display, but remove all the other data check boxes], include permissions, include categories d) private pages [same options as public pages].
If you already have Administrator role and it's saying you don't have permissions to RP to the remote site, setup your user on the target environment with the "Site Administrator" or "Site Owner" role.
A little late for first and foremost, but anytime you have something that's not working (remote publishing or otherwise), check the logs before you do anything else. The Liferay code base doesn't include a lot of helpful logging, but you do occasionally get a nugget of information that helps you piece together enough to do root cause analysis.
Cheers! HTH
I have a sharepoint MOSS 2007 Install on a server and need to move it to another new server. Can I just ghost the complete server to the new one or do I need to install and configure the complete server again?
Any suggestions appreciated.
As far as I know you will have to reinstall MOSS on the new server as during the configuration process many settings form the acutal server are stored to the MOSS configuration database. So just moving the MOSS software and database won't work. Even just renaming the server on which MOSS is running will probably lead to a MOSS error.
To make it easy to move MOSS to another server in the future you should think about visualization. By this you can move the server to every server you want just by installing the visualization software and moving the virtual machine to the new host server.
This strategy will also help you in case of emergency when the MOSS server crashes due to a hardware error.
Your best bet would be to do a clean install on the new machine. This gives you the freedom to properly configure your machine(s) - name databases, pick ports for the Central Admin, SSP etc.
Resist the temptation to "upgrade" to a newer operating system (2003 to 2008), a new database (2000 - 2005 - 2008) or add service packs or the infrastructure update. If it isn't installed on the current production system - then don't install it on your new machine. Make a mirror of what you have and it will be much smoother.
Once the new server is configured the way you want it - just do a full backup from the Central Admin page on the old machine - and run a restore from the Central Admin on the new machine. This will pick up all the customizations etc that you have on the old site.
Once it's restored - and you've tested it and it's working the way you expect, run a full backup from the Central Admin page on the new server. That becomes your baseline for moving forward.