I had an installation of SonarQube 5.4 running on Ubuntu (latest) against a SQL Azure database.
Since the upgrade to 5.5 it's not working anymore.
For the upgrade I deleted the data/es directory and updated the new conf file with my settings as advised.
The collation was wrong at first so I decided to try with a new db of collation SQL_Latin1_General_CP1_CS_AS.
Now it's looking for database_firewall_rules (table?) but cannot find it.
Any idea how I can solve that? Any table I could create?
Thanks!
You're hitting a known bug in SonarQube 5.5: SONAR-7589 . Until 5.5.1 or 5.6 gets released, you can temporarily use SonarQube 5.6-RC1 (available here).
Related
I have deployed a Service Fabric cluster with the Patch Orchestration application with version 1.2.1 using ARM following the link, it was successful without any issues with package 1.2.1. But same thing I tried with the package with the version 1.2.2, it is giving me an error "FABRIC_E_FILE_NOT_FOUND: The Application Manifest file 'ApplicationManifest.xml' is not found in the store."
Is it a known issue or could anyone help me out in this?
Thanks,
Avinash
In this case the issue was due to a different folder structure of the downloaded content. for me just changing the version to 1.2.2 and the url to the new version worked for the template.
I have a PostgreSQL 9.6.1 database from which I want to extract data for use in Excel with Get & Transform (PowerQuery). I have 64-bit Excel 2016 Pro Plus running on Windows 10 64-bit with .NET framework 4.6 installed.
When I try to use "Data->New Query -> From Database -> From PostgreSQL Database", I put the server name (localhost) and DB name into the dialog box.
I then get the error message,
An error happened while reading data from the provider: 'The type initializer for 'Npgsql.Counters' threw an exception.'
I have the following setup:
npgsql 3.2.0 installed with nuget. There are 3 versions of the DLL, net45, net451 and netstandard1.3. I used net451 for no other reason that it was closest to 4.6.
mono.security.dll 4.0.0.0. I added both of the DLLs to the global cache with gacutil.exe
I updated machine.config as follows for DbProviderFactories
add description=".Net Framework Data Provider for Postgresql Server" type="Npgsql.NpgsqlFactory, Npgsql, Version=3.2.0.0, Culture=neutral, PublicKeyToken=5d8b90d52f46fda7" name="Npgsql Data Provider" invariant="Npgsql" support="FF"
Could anyone help me understand if I did anything wrong?
It looks like this is an issue with a recent npgsql release? Until that's fixed, if you install version 3.1 or 3.0 Power Query should work :)
One other thing you could try is using net45. We officially support .NET 4.5.1 but sometimes you have more luck with older releases.
According to this article some support for older versions of Azure are going away:
https://azure.microsoft.com/en-us/blog/microsoft-azure-storage-service-version-removal/
We have a vs2008 application that is uploading files to Azure. {Using Azure 1.2 (for VS2008) - Microsoft.WindowsAzure.StorageClient v1.0.0 - Runtime v2.0.50727}.
We can't have this break since we are using this in production.
I need to know if there is a clear way to know if this is going to stop working.
I would really like to know if there is a way to upgrade the vs2008 project to use a compatible version of the StorageClient without migrating the project to vs2015.
Your version of the library should still be supported after the service removal. You can confirm which version of the service you are hitting by running requests through Fiddler and checking the x-ms-version. As you can see in the most recent post regarding our service deprecation, we are only removing version 2009-07-17 and older as of August 1, 2016.
If you've upgraded and EE site locally, and committed all of the changes through i.e. GIT, how are you supposed to upgrade the database on the production environment when you pull the upgraded codebase up to production? I've tried running the installer for the version the codebase is on but none of the migrations run. It says I'm already upgraded when the database is clearly still the older version.
The version number is stored in system/expressionengine/config/config.php.
$config['app_version'] = "273";
In order for the migrations to run you have to change that version to the old version you upgraded from.
My existing project, uses Azure .NET SDK 2.1. I wanted to upgrade the SDK to 2.4, so i dowloaded the latest from here for VS 2012. After successfull installation, when i opened up my solution, the cloud projects did not load. Thats ok, as they have been created using a lower version. So i removed them and created newer cloud projects.
But the thing which astonishes me is, there are many places in the worker role project where its throwing build error as it is not able to find out the assemblies and methods. Is there any easier way to upgrade to sdk 2.4 without making code changes. Which i think is a bad idea to make changes to the stable code, just for SDK upgrade.
When you open a project created using 2.1 SDK and try to open it using 2.4 SDK, you should see the project upgrade dialog which gives you the option to either download 2.1 SDK or convert existing project to target 2.4. Selecting the convert option should upgrade the project to 2.4. Any errors in this process will be reported in the project migration summary report.
If you are not seeing this dialog, then you might still have 2.1 sdk on your machine in addition to 2.4 sdk. In that case, you can go the Azure project properties. That will give you the option to upgrade your project to 2.4.
In regard to the build errors that you are getting for new projects, the error details will help in identifying the root cause.