We have submitted a UWP app, built using the Windows 8.1 SDK, to the Windows Store, published with the 'Private Audience' option. We observe that LoadListingInformationAsync (in the CurrentApp class) throws a 0x80190194 Not found (404) exception.
This happens regardless whether we run the project in Visual Studio or whether we install the Store version. The In-App products have been added, published and are all marked with 'In The Store'. We have checked that all the identifiers/names listed under 'App management/Identity details' match those in the manifest. We have checked that the In-App-Code works as expected with the CurrentAppSimulator. We have also used a network traffic monitor to check for network errors and haven't found any.
We have posted the same issue in the windows forum where it was suggested by a Microsoft employee to simply wait a couple of days. It is now two weeks since our in-app-products were published in the dashboard. This problem is blocking us completely and we definitely need help in fixing this issue.
Therefore we would very much appreciate if someone at Microsoft could find out why the in-apps published in the dashboard apparently haven't been installed correctly in the store and thus aren't visible from our application.
Here is our Package SID:
S-1-15-2-2762217728-2497590674-2702625719-1901796822-1169495103-2187450542-4267134542
Related
Sagemaker Studio worked flawlessly for me for the first 6 months. Then I started observing this issue. Screenshot of the error message
The screen holds up at this stage forever. Here's what I have tried:
Clearing my cache, even using a different machine. So I don't think the issue lies with the browser or my machine.
Pressing 'Clear workspace' in the screenshot above.
Shutting down all the apps in my sagemaker domain (excluding the 'default' app). This used to work initially but now this has stopped working all-together.
Created a new sagemaker domain with fraction of the files in the previous domain. Still, I see the same error message in the new domain as well.
This is severely affecting my work and I can't find a solution for this anywhere on the internet.
I've seen this issue before. Restarting the JupyterServer app and clearing out the EFS storage attached to your Studio domain helps.
Also, it is worth checking the JupyterServer logs to see what is causing the issue. Additionally, please make sure to use the latest version of Studio.
I have the following problem: I have a Laptop with two different user accounts (UserA & UserB / they belong to the same person but have different priveleges).
UserA: can build the solution and run tests locally (Everything is working as expected)
UserB: Has the rights to publish to the specific network drive, however he cannot build the project. The reason is that the Windows user itself has not the correct proxy settings configured, and thats why the nuget packages cannot be downloaded.
I have no possibility to change the proxy settings for UserB right now (It depends on internal processes, which might take a while)
However I would have expected, that when I build the solution with UserA, UserB would not need to build it again and just can publish it. This, does not work, as soon as I want to publish, VS tries to rebuild the solution and this does not work because some dependencies are missing and cannot be loaded.
Is there any solution for this problem? I tried to make a research, however I was not really sure for the correct keywords to search for.
Edit: I have now the domain added to my UserB, but I still have some other problems. However I found out that this article is heavily related to my issue: Unable to launch Visual Studio 2015 as a different user.
When I start Visual Studio via Command Line with the mentioned arguments, more works, however I am now not able any longer to connect to my database using Integrated Security = true in the connection string. But at least I can build now. Deploying also works but I just get a 500 Server error when I try to connect to the resource.
Edit2: I needed to add the domain to my user when opening Visual Studio with the command mentioned in the link above. This fixed my problem with connecting to the database.
Actually I do not need an answer anymore for my initial question but I will not delete it because maybe someone has an answer for a person who will have the same question later on.
When I have the AWS Toolkit installed, it takes a long time for Visual Studio (2015 update 2) to open.
Why? Because (as I saw using Fiddler) it's posting to 169.254.169.254/latest/dynamic/instance-identity/document like 9 times, and timing out every time.
I found this article which explains what that's all about.
But how do I turn it off? I really don't want to wait for so long for Visual Studio to load every time I open it.
The underlying SDK that the toolkit uses had a bug, fixed last week, where it was attempting to always fetch instance metadata to try and determine the AWS region (even when not running on an EC2 instance). I don't recall the version of the toolkit being built on that SDK version but it's possible.
A colleague posted an updated toolkit (1.9.6.21) this evening for an unrelated change - can you install this and see if you still see an issue? If so I'll take a look when I get into the office.
I developed my application with Qt 5.2.1 and MinGW compiler.The installer is created with NSIS and doesnt even require admin privilege.
I use blogger as my application's website, and post Google Drive links to download the setup files.
Suddenly Drive is now showing my application as a virus, even though I checked with virustital.com and the Windows anti-virus software.
I have not received any response to the post I submitted on their forum.
So I would like to know if there is any known common cause for this problem and whether that can be resolved.
PS: I have previously used the same Google services for another software that I developed few years ago, but never ran into such issues.
This is probably false-positive alarm.
Sometimes NSIS generated installer is recognized as virus (which is wrong).
Write to the AV company (I am not sure which AV software G drive uses) and report this problem - they should whitelist your software.
Sometimes simply rebuilding the installer helps too :)
Or my last idea is to remove 'dangerous' code from installer: many times inetC and various other internet calls are suspicious.
I'm trying to set up a NuGet server using ProGet and am hitting a brick wall when publishing a package and it doesn't appear in the feed. The package is written to disk and works in other NuGet feeds. Other packages also don't appear in the ProGet feed so I'm pretty certain that the package is fine and that the problem lies with ProGet.
I'm using the community version of ProGet, but I don't see why that would affect anything.
Any ideas are most welcome!
The ProGet service is responsible for indexing packages, so if it's not running, packages could be uploaded but not displayed in any feeds. Here are the common troubleshooting steps for this scenario:
Verify that the ProGet Windows service (INEDOPROGETSVC) is running.
Ensure that the user account hosting the ProGet service has access to the feed storage path. Since it is NETWORK SERVICE by default, it would not see your mapped drives, and may not have access to the UNC path where the packages are stored.
Try running the ProGet service interactively, i.e. stop the ProGet Windows service and run ProGet.Service.exe manually as a console application to see any live output. Remember to restart the ProGet service when you close the console application.
Check for feed indexing errors to see if there was a problem indexing a particular packages. I know in much older versions that single "poisoned" packages (bad .nuspec file, invalid directory structure, etc.) could halt the indexing altogether.
Thanks John Rasch, found that your first point gave me what i needed to look in the right direction.
I could not find the (INEDOPROGETSVC) service but I did find (ProGet Servie) - I restarted this and then refreshed the my feed and all the missing packages showed up.
My version of ProGet is v3.3.12
Thanks John.