EPrints Release: 3.3.15
I've been stucked cannot upload new docs for my eprints' existing record.
I CAN upload new docs if I create new Record (from Manage Deposit menu)
I've checked this troubleshooting URL https://wiki.eprints.org/w/Troubleshooting#System_gives_a_.22500_Internal_Error.22_when_viewing_advanced_search_or_submitting_a_document
Quote
System gives a "500 Internal Error" when viewing advanced search or
submitting a document
Possible cause: No Subjects, Bug in code.
Solution: Run generate_subjects
If this fails: Look at your apache error log for clues. If reporting a
bug, include the errors from the apache error log (often, but now
always, found at /usr/local/apache/logs/error_log)
But I CANNOT FIND the damn generate_subjects function/url/else...
I've googled around but nothing
Thanks for any helps/solutions
Related
I am new to Apache-Kafka.I am using:
zookeeper-3.6.0
kafka-2.13-2.4.1
Windows-7
Earlier i was able to create and list topics on the same machine.
After i restarted my system, i am unable to create and list topics.
I am getting below errors.
Create error:
Topic create error
List error:
List Topic Error
The error looks pretty simple. I googled a lot but unfortunately, i am not able to get a solution to this.
I followed the below link for configurations:
http://programming-tips.in/kafka-set-up-apache-kafka-on-windows/
Looking forward for some expert advice.
Type it out manually and it will work.
There is something wrong with the '-' in the example code.
We have an api deployed on Azure that uses Google authentication. Over the weekend, the API started to throw 500 errors that were resolved after restarting the API. Is there a way to identify what the underlying cause for these errors might be?
Check if you have custom error mode in web.config file to “on” or “Remoteonly”. If
yes then turn it off. Add the following line to System.web element in web.config
Enable custom logging/instrumentation in the code which can help you in more
information.
ASP.NET applications can use the System.Diagnostics.Trace class to log information to
the application diagnostics log. For example
System.Diagnostics.Trace.TraceError("If you're seeing this, something bad happened");
Enable Detailed Error Messages - Detailed version of the html files produced when
your website responds with an error message. This is good to enable for debugging
some error responses in your website. It is stored in the website's file system.
Web Server Logging - Also known as HTTP logs or IIS logs, this will log all requests
to your website in W3C Extended Log File Format.
Failed Request Tracing - Also known as FREB, here you can get lots of information
from IIS through its different stacks for each failing request.
Try to troubleshooting QuickBook's Web Connector by following helping URL: Click Me. When I try to Add an application into Web connector getting following error: "QBWC1048: QuickBooks Web Connector could not verify the web application server certificate. QBWC1051: The new application was not added"
QuickBook throws the 1048 error because it is unable to complete a GET request at the AppURL that specified QBFS.qwc file. This is because test.developer.intuit.com restricts GET requests via the SOAP API.
To get around this, include a parameter in the .qwc file, and set it to the same value as your AppURL without the URL path.
For example, if your AppURL is https://mycompany.cs1.force.com/services/Soap/class/myApiClass, then set CertURL to https://mycompany.cs1.force.com.
This is the solution suggested by the QBWC log file, and it worked for me.
Reference URL
I found I had this problem because my software was trying to load the file
http://developer.intuit.com/uploadedFiles/Support/QBWebConnectorSvc.wsdl
which no longer exists. :(
So I got a WSDL from
https://test.developer.intuit.com/QBWC/TroubleshootWebServiceFS/Service.asmx?wsdl
and put it in my Site's root directory, then changed my code to point there, and it worked.
I am trying to add service reference to Visual Studio for REST API.
The demo URL given to me by a DocuSign support engineer is as below.
https://demo.docusign.net/restapi/v2
But when I try to add it, I get the following error.
Do I need to add anything to web.config? Thanks in advance. I already have details related to SOAP in web.config. I added a second API URL string.
The document at the url https://demo.docusign.net/restapi/v2 was not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from 'XML Schema' is 'Data at the root level is invalid. Line 1, position 1.'.
- Report from 'DISCO Document' is 'Data at the root level is invalid. Line 1, position 1.'.
- Report from 'WSDL Document' is 'There is an error in XML document (1, 1).'.
- Data at the root level is invalid. Line 1, position 1.
Metadata contains a reference that cannot be resolved: 'https://demo.docusign.net/restapi/v2'.
There was no endpoint listening at https://demo.docusign.net/restapi/v2 that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
The remote server returned an error: (404) Not Found.
If the service is defined in the current solution, try building the solution and adding the service reference again.
I recommend using the open source DocuSign NuGet package if you're using .NET / Visual Studio:
https://github.com/docusign/docusign-csharp-client
You can install it in seconds from the Tools menu and it will install the dependencies and references for your project automatically, then you can add your using statements in your code.
To get started follow the README.
I recently setup Proget to try its nuget and chocolatey servers. Now when I try to publish packages to nuget feed through a teamcity build, I keep on getting error "proget Failed to process request. 'There was an error processing the request: Invalid API key.'.". I've made 100% sure that the name and password are working fine and specified API key as per Proget doco (i.e. username:password ) . THat feed already has one package which I published on the day I installed Proget for trying out. What could have gone wrong?
I found a work around.
[1] I confirmed that my username:password combination is correct.
[2] Then I renamed that original feed to feed_old (or whatever you
want or even delete it if it doesn't have anything important in it) I
had created for trying out and which wasn't allowing publishing
through teamcity and giving the error message as per the question's
message.
[3] Created new feed with the name I wanted.
[4] Confirmed that the username I was using in API key had necessary
privileges to publish to this new feed I just created.
[5] Then tested the publishing to this feed through teamcity and
VOILA!! it worked.
I don't know why this happened in the first place though. It would be good to find out and be able to fix underlying reason rather than using the above mentioned workaround.