BlackBerry app update approved but not in App World - blackberry-playbook

I updated my PlayBook app in App World to Version 1.1, but it doesn't show up in App World. Version 1.0 is still there. In the Vendor Portal, it shows Version 1.1 approved, but now Version 1.0 is denied. What's going on??

It does take some time to update download caches and synchronize all databases.
Just wait for a few hours/days and everything will be fine. :)

Related

Application Insights extension breaking Azure web app

I had Application Insights running smoothly on an Azure Web App via the AI SDK, reporting to an AI instance hosted in Azure.
The only niggle was it didn't show detailed dependancy diagnostics, according to this page this was because I was using the SDK only, I needed to "Instrument your web app on the server", which looking at the docs can't be done if you already have an instance of AI running....helpful!
Reluctantly I deleted the AI instance, stripped the SDK from my code so I was starting fresh, and followed the steps, however as soon as I finished the process in the previous link my website broke and now responds to every single request (MVC5 and Web API) with an empty 404 request
The AI status page is showing green ticks for everything, and I can't discern anything from diagnostic log dump from KUDO or manage to remotely debug the site.
Deleting the AI extension under Web App -> Extensions in the Azure portal and then restarting the web app fixes the problem.
I've run out of ideas on how to fix this, is there anything else I can do to get to the bottom of the problem?
To fix this problem, delete the following 2 files from your web app's (or slot's) filesystem:
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation32\ProductionBreakpoints_x86.config
D:\home\siteextensions\Microsoft.ApplicationInsights.AzureWebSites\Instrumentation64\ProductionBreakpoints_x64.config
You can do this easily through Kudu.
Edit: Apparently this is/was an issue with the ProductionBreakpoints interacting with precompiled views. Microsoft has informed me a fix should be out within the next couple days. The version of Application Insights extension I have now that is still broken is 2.4.6 - I will post the "fixed" version when I can confirm it.
Edit 2: Confirmed this is fixed in 2.4.7 which is out now.

JavaFX application won't start when running JNLP form website

I have created a JavaFX 2.2 application that I am trying to deploy using web start. I singed the application with a proper certificate (not self-signed) which I actually use for another Swing application for another client of mine. I used this certificate because I still don't have the new one for this client and I wanted to test the process.
I use Netbeans 7.3, JDK 7_21 and JRE 7 _21. I pack the application using Netbeans with all the necessary settings for a web start application. I can run my application locally on my and others PCs and its working fine.
The problem starts when I upload the application on the clients website. Website link works fine, JNLP is downloaded fine but when I run it I get a Runtime error. Click here for details but there are no actual details in the console. Any ideas would be much appreciated
Thanks
Nevermind whoever took the time to read my question. I wasn't including the codebase setting in my jnlp. Added and working fine.
Thanks for your time

Windows Azure version backward

Today, I checked my windows azure website (built with a web service) And the version was not the same as yesterday. It's very strange, it seems that ther version went backward.
So I took my project in VS and reuploaded it. Then it was good
I am quite scared, is it a normal behaviour, I think not. But how to stop this behaviour. If I remember well it's not the first time it happens to my project.
Thanks a lot for your help.
Internally if there is any problem within Azure, It is the nature of Azure to Remove the troublesome VMs and Deploy a new VM with the "cspkg" File that we upload during application deployment either through Azure portal or through Visual studio directly.
In case You make any changes through RDP to the deployed application, there is no guarantee that the application will retain the Changes.
Further more if you face this again, it is better to contact Microsoft Support, They should help you out.
Here is the explanation of the Microsoft Support :
Any changes made with Web Deploy are temporary. It can only be used for development and testing and not intended for updating applications in production. When the role instance is restarted, the changes will be gone. We would suggest that you upgrade the deployment by uploading package files from the management portal or disabling WebDeploy while deploying.
You can read more about Web Deploy here http://blogs.msdn.com/b/cloud/archive/2011/04/19/enabling-web-deploy-for-windows-azure-web-roles-with-visual-studio.aspx.

Why do I get 403 on my Azure MVC3 site unless I change OS to Win 2008 R2?

I have recently updated to the latest SDK 1.7 and made some changes to my MVC3 app. When I publish to Azure I now get a 403 on all pages.
If I go to the Azure Portal and change my web role to use OS Windows 2008 R2 the error goes away and my app works. However every time I re-deploy I have to change the Role to use 2008 R2 any ideas?
Is it a Web.config issue that the later version of IIS handles? Any idea what to change to get this to work again?
I don't think I have made any routing changes etc.
I'm sorry I can't answer why this issue is happening, but you can change the default OS so you no longer have to update the OS every time you deploy. MS have a full description of what to do.
The short version is open you service config (.csfg) file and update the ServiceConfiguration node so it contains the element osFamily="2" and also osVersion="*" e.g. :
<ServiceConfiguration serviceName="MyCloudProject" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="2" osVersion="*">

Problems with ASP.NET State Service version; state service is 1.1, website is 3.5

I have a ASP.NET 3.5 website running on Windows Server 2003 and I'm using the ASP.NET State Service to manage sessions. It will appear to be working then I regularly get an error saying my code needs to have version 2.0 of the State Service running to work (I think that's what it said, I've temporarily switched back to storing sessions InProc). Refresh the page and the error goes away (for a bit, it's bound to come back).
So I looked at the properties of the ASP.NET State Service in the Services interface and it's mapping to a .exe in the 1.1 framework folder:
C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet_state.exe
There's a corresponding version in the 2.0 framework folder, but I don't know how to add it as a new service. I'm also not sure that adding the 2.0 version (and stopping and/or removing the 1.1 version) will solve the problem.
Thanks in advance for any help anyone can provide.
Mick
I had a similar problem running ASP.net 4 side by side with ASP.net 2.0 on Win Server 2003 SP3 and all in 32bit mode.
At some stage something nuked the ASPNET_State from the C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory but had failed to tell the ASPNET_State server that it should now be pointing to C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\ASPNET_State.exe. I can only imagine it was when .Net 4 was installed but I can't be sure.
So I ran
sc config aspnet_state binpath= C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_state.exe
and it all seemed to work fine after that.
(Please note the space after 'binpath= ' - I fear the person who made the original post (Mick Byrne) did not put this in and thus explains why... "However this just doesn't work at all and just brings up the usage instructions for this branch of the 'sc' command" - see comments in original post)
OK, found a solution somewhere else that appears to have worked. Almost the same as the above answer:
Go to .NET2.0 directory in command prompt
run 'aspnet_regiis -i -enable'
computer sits there chewing for a minute and then it all seems to be working.
I checked the 'ASP.NET State Service' in the Services console and it's now pointing to the .NET2.0 version (not the .NET1.1).
The only strange thing I did that may have led to this scenario was to install .NET3.5 straight onto a box that previously only had .NET1.1 installed. I figured it would put .NET2.0 in along the way (which it kind of did), but must have forgotten about the session thing.
You can run aspnet_regiis -? From the framework 2.0 directory to update the web site.

Resources