I have a problem setting up the environment in my Spring tool Suite. It's as simple as not being able to start the server successfully. Because whenever I start it, it returns this error:
Error: Could not find or load main class
Workspace.sts-bundle.pivotal-tc-server-developer-3.1.1.RELEASE.base-instance.conf.logging.properties
I am using the 3.7.0 release of STS. What could be the possible reason for this? Any suggestions?
This is the same as here: Pivotal tc Server v.3.1 won't start
Make sure there are no spaces in your path to STS and let us know if that resolves your issue.
Thanks.
Related
I have an old Debian Compute Engine instance (created and running since December 2013) and got an email warning about the turndown of Legacy GCE and GKE metadata server endpoints (more details at https://cloud.google.com/compute/docs/migrating-to-v1-metadata-server).
I followed the directions for locating the process and found that the requests were coming from /usr/share/google/google_daemon/manage_addresses.py. The script seems to be the same as what's at https://github.com/gtt116/gce/blob/master/google_daemon/manage_addresses.py (also with what's in that directory).
I don't recall installing this, so I'm imaging it came with the provided Debian image I used in 2013.
Does anyone know what this manage_addresses.py script is, what it does, and what I should do with it now that the legacy metadata server endpoints are turning down? Is it safe to just stop running it? Or is there a new script I should replace it with? Or should I just try to update it myself to use the new endpoint?
I dug around and was able to trace /usr/share/google/google_daemon/manage_addresses.py as being installed by a package called google-compute-daemon. A search for that brought me to https://github.com/GoogleCloudPlatform/compute-image-packages#troubleshooting which explains that google-compute-daemon has been replaced with python-google-compute-engine. That led me to https://cloud.google.com/compute/docs/images/install-guest-environment . I followed the instructions there and manually installed the guest environment.
I noticed during installation that it said it was removing the google-compute-daemon package (and a packaged called google-startup-scripts), so this seems like the right thing. And I'm no longer seeing any requests to the legacy endpoints. So it seems like at some point the old guest environment failed to update.
TLDR; If you have this problem, follow the instructions at https://cloud.google.com/compute/docs/images/install-guest-environment#installing_guest_environment to manually update the guest environment.
I have a problem with configuring standalone custom registry in WebSphere Application Server (Cluster environment). I have followed all steps from IBM manual:
I have implemented UserRegistry interface in DataBaseRegistry class
I have copied .jar to the lib/ext folder of WebSphere
I have assigned all necessary properties on Global Security page
and while trying to assign Standalone Custom Registry as current I got a following error:
Validation failed: Error occurred in RequiredModelMBean while trying to invoke operation getUsers
The funny part is that I followed all of those steps in a standalone version of WebSphere (not clustered) and it is working properly (so the problem is not in the code). Another thing is that there is nothing in the log files. I can see that getUsers is called and then no Exception or anything.
UPDATE: I resolved my problem. I was propably not 100% focused.
It tourned out that I forgot to copy additional jar with JDBC drivers to lib/ext that allow to connect to MSSQL.
LESSON LEARNED: Do not start important configuration work on Friday after lunch ;)
Annoying issue...
OS : Linux
I am trying to connect to couchbase server but its causingfollowing exception. Problem is that everything was working fine and this issue has starting coming from no where. I hope its nothing to do with some port configuration or related to it...
If some one have any useful information over this, Please share with me. in the mean time, I am also looking into the issue.
Exception Stack Trace :
2014-11-16 07:57:00.946 WARN com.couchbase.client.CouchbaseConnection: Problem handling Couchbase IO
java.io.IOException: Invalid argument
at sun.nio.ch.DevPollArrayWrapper.poll0(Native Method)
at sun.nio.ch.DevPollArrayWrapper.poll(DevPollArrayWrapper.java:170)
at sun.nio.ch.DevPollSelectorImpl.doSelect(DevPollSelectorImpl.java:68)
at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)
at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
at net.spy.memcached.MemcachedConnection.handleIO(MemcachedConnection.java:398)
at com.couchbase.client.CouchbaseConnection.run(CouchbaseConnection.java:288)
I tried connecting to the same couchbase server from a sample program from my local windows box, It worked as expected.
Got the reason. I was using -d64 option while calling my java program. unfortunately, the couchbase sdk I am using was only supporting 32 bit.
I removed the -d64 option and it ran fine.
Details:
I am using activeCollab, have installed it on cPanel shared server.
Unable to send emails via native php mail function, even if i try to configure STMP i get the error. so i am not able to configure SMTP either.
Not sure where i am going wrong.
Version:
3.2.12
Error:
Failed to connect. Reason: Failed to load class 'Swift_1_SimpleCharacterReaderFactory'
Failed to send message. Reason: Failed to load class 'Swift_1_SimpleCharacterReaderFactory'
That is not a known issue, so we recommend that you upgrade to the latest stable release (3.3.18 at the moment). You can find the upgrade instructions here.
Upgrade should resolve the potential problem that you did not upload all the files properly, plus activeCollab 3.3 has auto-upgrade feature which will make similar error less likely to happen in the future.
I have a page on the server and i tried to run it like this article:
http://www.eggheadcafe.com/articles/20010328.asp
then I get an error:
Executed as user: NT AUTHORITY\NETWORK SERVICE. The step did not
generate any output. The step failed.
When I try to edit the script I get another error:
Creating an instance of the COM component with CLSID
{AA40D1D6-CAEF-4A56-B9BB-D0D3DC976BA2} from the IClassFactory failed
due to the following error: c001f011.
(Microsoft.SqlServer.ManagedDTS)
When I run the asp page manually it works fine! do you know what can be wrong?
I would apply the most recent service pack for SQL Server both to your server and to the workstation(s) where you use Management Studio. The error you mentioned has been fixed: http://connect.microsoft.com/SQLServer/feedback/details/557402/ssms-can-no-longer-create-or-edit-job-steps
This will fix the problem when you edit the job step in Management Studio. There are some other workarounds (e.g. re-register some DLL, or restart Management Studio), but those are only temporary. You can also disable UAC, but you may have that feature enabled for a reason. The real fix is to apply service packs / cumulative updates to fix the underlying code.
As for the error message from the job, there could be a number of things going on. Who is the owner of the job? Who is the user executing the VBScript? What exactly is the job doing?