I checked the latest versioned 202212 API with Postman. It shows "projection parameter is not allowed for this endpoint" error.
202212 API
Nov and Dec versions do not support projection, but Jun to Oct versions do. However, Nov and Dec documentations still include projection page, which confuses me. Do it mean LinkedIn API will not support projection anymore? Or is it my request url issue? Are there any other ways to do projection?
Related
I've just downloaded a fresh copy of Eclipse Version: 2022-09 (4.25.0) Build id: 20220908-1902 and fired up the Marketplace client to install Spring Tools 4 (4.16.0.RELEASE).
Edit: I should add that I used the same workspace as the previous version and chose to convert it for the latest version when prompted
I clicked "Install" and kept only the required features and then clicked "Confirm" and accepted the license agreements, then clicked "Finish".
While waiting for it to download and install, a "Trust" dialog popped up saying the two items have expired. One is "Pivotal R&D" and the other is "Pivotal ", they expired back in 2020 and 2018, respectively.
A Google search did not turn up similar issues reported by anyone. I'm not behind any firewall, proxy, or VPN. I would like to know how to proceed with the install without having to trust these expired certificates.
Dialog showing expired certificates
I filed an issue for this here: https://github.com/spring-projects/sts4/issues/852 - we basically need to update the signing information for those pre-built third-party bundles that we include in the Spring Tools 4 distribution builds.
In the meantime, unfortunately you need to trust the expired certificate to get the bundles installed.
VS2017 shows this error when I'm trying to upload my apk:
This API has been deprecated and is no longer available
Any idea what cause and how to solve this error?
Xamarin 4.12.3
("Since I am answering as a guest it is not allowing me to embed images so there are image links below")
The issue happens in vs2019 also and I think it is being caused by this message in the Google Play Console
ACTION REQUIRED: Your automated publishing to Google Play will stop working on December 1, 2019
Your app is using an old version of the Google Play Developer API. From December 1 2019, versions 1 and 2 of this API will no longer be available, and any calls to these versions will fail. Update to version 3 before this date. Learn more
I am not sure how to fix this yet but if you need to get a release out you can manually grab the apk and upload it to the google play console.
Archive Manager > click on the desired apk > click open folder > grab apk file from the "signed-apks" folder
you can then go to the google play console and create a release and manually upload the apk file along with your newly created release.
I know this is not the fix I just figured I would through it out there in case it can help anyone.
Same Error Message in 2019
Same Message (VS 2019, 16.3.10; all Nuget-Packages updated, etc.)
I'm pretty sure it's the upload from within VS that is using an old API Call. Until now I didn't get a confirmation from MS Support - still waiting for it.
https://developercommunity.visualstudio.com/content/problem/844304/api-has-been-deprecated-410.html
Microsoft patched this bug in the new version 16.4.2 of Visual Studio (see patch notes).
Please make sure to update to this version to fix the problem.
We have a small business and just bought Server 2016 Essentials to run Sage 300. When trying to install Sage 300, it says : "Unsupported Environment - Sage 300 does not support installing on a DC". That's a problem because Essentials Server must be a domain controller. But then says that some features won't work (features we won't use) and gives me the option to proceed anyway. I proceed, but the it doesn't run : "the server the unable to process the request due to an internal error". So, my question is: Can Sage run on Server 2016 Essentials? If not, can I upgrade Essentials to Standard and NOT use/install a domain? Right now we only use the server as a file share. This is a small office and we just wanted a file server to run Sage.
The bottom line is that it is possible to run Sage 300 on Server 2016 Essentials.
I was able to click by the "unsupported environment" error and it installed just fine. The Sage website has conflicting information on whether it will run or not but we are running it successfully.
The 2nd error was caused by a bug in our version of Sage, in which a service was not starting correctly (it needs to be manually restarted as a work-around).
Once I did that, everything ran perfectly.
While trying to integrate R Studio with SQL Server 2016 I am getting following error:
Unable to launch runtime for 'R' script. Please check the configuration of the 'R' runtime.
As suggested on different sites it is advised to install "%programfiles%\RRO\RRO-3.2.2-for-RRE-7.5.0\R-3.2.2\library\RevoScaleR\rxLibs\x64\RegisterRExt.exe" /install.
But I have already installed R studio and not able to find the path specified.
R Services for SQL 2016 is a new offering from Microsoft - who purchased Revolution Analytics about a year ago. This is the first major result of that.
SQL Server 2016 is in (CTP - community technical preview), so not really finished (although you can download and use a version that will expire after about 6 months). Also a lot of the docs are incomplete and there are probably a fair amount of bugs. However it has been long announced that it will include "R Services for SQL 2016", which is based on the Revolution R Engine. In order to use that you have to
Install SQL Server 2016 CTP as usual.
Install the "Advanced Analytics Extensions" from the setup.exe program (see https://msdn.microsoft.com/en-us/library/mt590808.aspx)
Obtain the appropriate RevoScaleR packages (there are two) and install them, one your client, and one on the machine running SQL 2016. They are described here: https://msdn.microsoft.com/en-us/library/mt604883.aspx
Then to test it you can follow the instructions here: https://msdn.microsoft.com/en-us/library/mt590808.aspx
Good luck with it, but remember it is still in pre-release development and testing, so problems are to be expected.
In Tridion 2011 SP1 GA, I constantly am getting this strange error at random times.
Publish a page, page is successfully written to the file system, but in the publishing queue it would be stuck in "Waiting for Deployment"
One day it would be successful and the next it would be stuck.
Any ideas why this is happening?
This could be happening because your transport service has stopped polling the deployer because the polling intervals/max poll time which are configured in the the Transport Service configuration file reach their limits. Assuming that is the case, the Deployer has continued to deploy files, but the Transport Service has given up checking. However, I would expect to see the status eventually report failed in the Publishing Queue.
It is not clear if you are using GA or SP1 of SDL Tridion 2011. There are a number of hot fixes which will help solve these issues for GA and HR1, all of which are bundled into SP1. Specifically these solve some issues relating to returning responses to the Transport Service after some sort of (non-catastrophic) failure in the Deployer after it gets a large queue of items or a a particularly large transaction to deal with. I strongly suggest you install the latest patches that before trying to adjust the behaviors through configuration.
If you have already applied all the patches, please double check that you have applied them correctly (copied all the new jars etc) to the CD side (Deployer and Broker etc) as well as the CM side.