Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QGIS Crashing When Connecting to datasets in MSSQL #20932

Closed
qgib opened this issue May 27, 2015 · 5 comments
Closed

QGIS Crashing When Connecting to datasets in MSSQL #20932

qgib opened this issue May 27, 2015 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority

Comments

@qgib
Copy link
Contributor

qgib commented May 27, 2015

Author Name: Richard G (Richard G)
Original Redmine Issue: 12837
Affected QGIS version: 2.8.2
Redmine category:data_provider/mssql


Using QGIS I have connected to a database from MSSQL with no issues.

When I import one feature I can specify the coordinate system and edit attributes. However, if I wish to add a second feature and do the same I constantly get the following error message: "Crash dumped - minidump written to C:"

In Add MSSQL Table(s) I have the following information:

[Schema: sde] [Geometry column: Shape/SHAPE] [SRID: 5 digit code] [Primary key column: (Blank)] [Select at id: (Checked)] [sql: (Blank)]

Does anybody know what may be causing QGIS to crash?


Related issue(s): #19299 (duplicates)
Redmine related issue(s): 10946


@qgib
Copy link
Contributor Author

qgib commented May 27, 2015

Author Name: Giovanni Manghi (@gioman)


Did it worked fine with previous qgis releases?


  • crashes_corrupts_data was changed from 0 to 1
  • category_id was configured as Data Provider/MSSQL
  • status_id was changed from Open to Feedback
  • fixed_version_id was configured as Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented May 28, 2015

Author Name: Richard G (Richard G)


Hello thanks. It did not work for me in 2.6. It does however work for me in 2.2.0 Valmiera. Any thoughts as to why it is not working for me in the latest versions of the software?


  • assigned_to_id was configured as Giovanni Manghi

@qgib
Copy link
Contributor Author

qgib commented May 28, 2015

Author Name: Giovanni Manghi (@gioman)


Richard G wrote:

Hello thanks. It did not work for me in 2.6. It does however work for me in 2.2.0 Valmiera. Any thoughts as to why it is not working for me in the latest versions of the software?

yes, is called bug :)
Sorry I can't do tests of my own, I don't have/do MS SQL Server.


  • assigned_to_id removed Giovanni Manghi

@qgib
Copy link
Contributor Author

qgib commented May 28, 2015

Author Name: Saber Razmjooei (@saberraz)


Did you check this #20502?

@qgib
Copy link
Contributor Author

qgib commented Jun 13, 2015

Author Name: Giovanni Manghi (@gioman)


Saber Razmjooei wrote:

Did you check this #20502?

that should be duplicate of #19299
Please reopen if necessary.


  • resolution was changed from to duplicate
  • status_id was changed from Feedback to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! High Priority Data Provider Related to specific vector, raster or mesh data providers Crash/Data Corruption labels May 25, 2019
@qgib qgib added this to the Future Release - High Priority milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Crash/Data Corruption Data Provider Related to specific vector, raster or mesh data providers High Priority
Projects
None yet
Development

No branches or pull requests

1 participant