this question is about PageFlex StoreFront server crash and recovery. We were able to recover the OS Drive and all Storage. We moved it via clonning to a new box.
The License Administrator displays the Host Server and License as OK -- no errors. The software runs as it always has except we have this error in event viewer regarding the PFLicenseServer Service:
PFLicenseServer
Computer: WEBSERVER
Description: Licensing failure: Not enough licenses for Pageflex Server Job machine 'WEBSERVER'.
And yet the License Administrator displays OK!
On reboot a Service startup problem alert popsup. Any ideas how I can resolve this? I've scoured the registry and the path to the Service is correct. So I'm at a brick wall.
A few things you can check:
Server Admin
- Is the host that failed still in the list of hosts?
- Does the failed host still have engines it can run? Try setting Minimum Idle Engines and Maximum Concurrent Jobs to 0.
- Host logs
Licensing Administrator:
How many CPUs are in use?
More information on what version of Pageflex you are running would be helpful. Also is this a server license or are you running storefront? If Storefront, does this come up successfully?
Related
All the trick seems to be that I'm under AWS.
I found many solutions to solve that problem as connection can be made directly on the server. The issue I have is that I'm running the server on AWS, therefore, only RDP connection is available.
As the server is part of the domain , I added the server as part of the server manager ones on my Domain controller.I tried several times to install/uninstall the RD diagnoser AND the RD License manager. When I try to run each one, I get " Server Manager can not open the tool
Checked with Powershel,, the component install is properly done ( or at list seems to for the system ).
I tried to reset the grace period for RDS server ( info here: https://mangolassi.it/topic/19353/reset-120-day-grace-period-for-windows-rds-server-with-powershell but no effects.
I would need first to get back access to a session, which could be a good start
Thanks for your insights
At $employer we have a customer trying to run NiFi on Windows 2012 server. We have helped them configure it as a windows startup task using the Task Scheduler. I realise this may be more of a ServerFault question but there's nothing much about NiFi on there.
When this is run as user with local admin rights, it runs perfectly. When run with the user created specifically for this service (with the required "Run as a batch" permission), it starts up and then promptly shuts down with a permission denied error on a TCP connect.
Is there a specific Windows permission that is needed for NiFi to run as a batch and listen on TCP ports?
On *nix systems, if the TCP port is below 1024, you need to run as root. I am not sure if this applies to Windows systems as well (surprisingly little documentation to answer this common question directly), but that could be the cause -- when run as an Administrator this works; when run as another user it fails. Can you share the explicit error you get from the nifi-bootstrap.log and/or nifi-app.log files?
So this is with some of my Windows Remote Desktop License Servers, which I am using with Microsoft Azure Cloud Subscription.
The issue I am facing is related to the license expiry. A fully functional and activated 2012 Remote Desktop Session Host server displayed the following message:
"THE REMOTE SESSION WAS DISCONNECTED BECAUSE THERE ARE NO REMOTE DESKTOP LICENSE SERVERS AVAILABLE TO PROVIDE A LICENSE.PLEASE CONTACT THE WINDOWS ADMINISTRATOR"
This was a simple setup on one server with the: connection broker, Session Host and Licensing server with 2012 CAL’s installed. And though the licensing seems to be configured correctly, in server manager.
But with the CAL(client access license), every user logging on to Server, gets the error message mentioned before. For every user, I need to update the CAL license again and again, and this issue occurs every 30 or 60 days. Kindly suggest something, and feel free to ask more details on this, if needed.
Step 1: The solution is delete the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
Step 2: Try connecting in again.If it doesn’t work and you get the following error message: “The remote computer disconnected the session because of an error in the licensing protocol“then all you need to do is Right-Click on the Remote Desktop Connection icon and select “Run as Administrator“.
I am having issues getting the Event logs to forward to my collector server. I have followed various articles on how to set this up and, enabled winrm on the source and wecutil on the collector. I ensured the collector was in the Event Log Readers Group, and the windows firewall rules were enabled, however the firewall is not enabled. I have set up the subscription properly with collector initiated and machine account for the user account, however No events show up in the "Forwarded Events" log, and the runtime status fails with the following error:
Error - Last retry time: 10/12/2016 8:55:12 AM. Code (0x80338095): The connectivity test from the push subscription source to the client failed. This can happen if the client machine initiating the push subscription is unreachable from the server machine where the event source is located. Possible reasons include firewall or some other network boundary. Modify subscription to use Pull based subscription. Next retry time: 10/12/2016 9:00:12 AM.
I haven't found much on the web to troubleshoot this. Are there any steps I can take to determine the issue, or am I missing something simple? One technet article talked about a hotfix for 2008 servers, mine are all 2012. Could it be GPO related?
Used the following article to troubleshoot various parts of the process.
http://tutorial.programming4.us/windows_7/forwarding-events-(part-2)---how-to-troubleshoot-event-forwarding---how-to-configure-event-forwarding-in-workgroup-environments.aspx
Ended up deleting the subscription and re-creating it and the events started to forward.
I just changed the Event Delivery Optimization back to Normal, then ran the command wecutil gr <Subscription name> and it looked like it worked.
Hey all,
I'm having trouble with PerfMon on one system out of fifteen in a development environment. Accessing it from the local machine is fine but connecting to it remotely throws a "Cannot connect" error.
Each machine is running Win 2003, is connected to the same domain and I have admin rights to all.
There were some services set to disabled which are normally enabled by default so I've set these to match the other machines on the network - still have the same problem.
Any ideas?
Cheers
**Update**
Ok - I found it was the remote registry service not running correctly causing the above error; Once that was enabled Perfmon is now telling me "No such interface supported".
If I connect through Computer Management, it fails the first time, but the second attempt is successful. Connecting through perfmon fails everytime.
Fixed - for anyone that runs into this issue, hopefully this can help you..
Enabling Remote Registry fixed my first problem.
The second issue, "No such interface supported" turned out to be permissions issues within the registry. Apparently the machine had some pretty obscure permissions set to specific registry keys a long time ago, which are now irrelevant.
Resetting permissions with secedit fixed it up -
secedit /configure /cfg %windir%\repair\secsetup.inf /db secsetup.sdb /verbose
Perfmon counters are now accessible remotely.
We encountered the second issue - "No such interface supported" when attempting to "Connect to another computer" in Performance monitor.
All the rules and services are running.
We found the following:
If the user was added to the local admin group, they were able to connect to another computer (irrespective of belonging to the Performance Monitor group).
If the user was not a local admin and in the performance monitor group - we were unable to connect to another computer via the "Connect to another computer" context menu.
But we were able to add the performance counters. In Performance monitor when you add a counter there is an option to "Select counters from computer". We were able to connect to the counters on the remote machine this way. Also note that if you are planning on data collecting, you would need to set the correct credentials (by default it appears to run under a local system user).
I fixed my case as follows:
Add Firewall rule Performance Logs and Alerts from the predefined rule list.
From client, run the Performance Monitor as the remote user
Eg: runas /user:remote_machine\username "mmc perfmon.msc"
Of course, the user must be at least in the user groups "Performance Log users" or "Performance Monitor Users".
The reason why perfmon.exe do not want to connect to the remote server is, it wants to connect to the Perf Monitor and the Perf Logs (Data collections).
So you have to add the user account to also the Log User group and of course to the Monitor Users.
you don't need to be local admin on the remote server!