encryption – ODBC 32 System DNS username and Password greyed out

I have a legacy app that uses a default System DSN configured account. This System DSN is pushed to all desktops via a GPO. The GPO has three sections to it

  1. a desktop shortcut
  2. Computer Configuration/Preferences/[![enter image description here][1]][1]Control Panel Settings/Data Sources/ the action is set to Create so any new computers added to the domain will get his GPO. These are Registry settings that build the System DNS
  3. Under Computer Configuration/Windows Settings/Scripts/Startup and in the Scripts tab there is a VBS file that has the username and password in them. The password is encrypted.

I need to update the password and have no idea how they got the existing password encrypted in the VBS file. I understand why the settings are greyed out. I’m trying to figure out how they got this to work.

Any suggestions would be greatly appreciated

sql server – Continuous windows events 4648 and 4624 generated when ODBC driver is configured with Integrated windows authentication

We are running a C# application in my VM,which is configured to run as a windows service. The service runs as local system account and talks to a locally installed SQL database server. I have access to the source code of this application.

I am seeing that this application is generating 4648 and 4624 events every 4-5 seconds. For example — Event 4648

A logon was attempted using explicit credentials.

    Security ID:        SYSTEM
    Account Name:       WIN-NGGM12KCB4T$
    Account Domain:     DomainName
    Logon ID:       0x3e7
    Logon GUID:     {00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
    Account Name:       DomainUser
    Account Domain:     DomainName
    Logon GUID:     {a17ff1a5-bd09-a254-fd6d-20ce35788bf5}

I played around sometime and found that this because of the SQL server ODBC driver which is being configured with our product database. When this driver is configured with “Integrated Windows authentication”, it generates these continuous events. However, if you configure this driver with “SQL Server authentication”, you will not be seeing these messages. We are using SQL Server Native Client 11.0. Is there any way to suppress these messages ?enter image description here

postgresql – Postgres: ODBC: ERROR: SSL connection has been closed unexpectedly; Error while executing the query

I’m currently in Australia and so is the database.

Staff attempting to connect to the database from overseas (USA, UK) consistently run into the error: ERROR: SSL connection has been closed unexpectedly; Error while executing the query, when they try to connect. People here can connect fine without that error but anyone overseas will receive that error if their query lasts longer than say 1 minute?

The database is a postgres RDS hosted in AWS Sydney region.

What is the cause of an SSL connection closing like this? Is it the server or is it just caused by the latency of someone overseas trying to connect to the database? Is there any way to combat this?

This error was from an ODBC connection using Power BI or Tableau
We find a similar error when querying from Python or DBeaver as well.

Excel com dados ODBC – Stack Overflow em Português

Boa tarde,

É o seguinte, a empresa onde trabalho, trabalhamos bastante com excel e estes com base de dados ODBC, e o que eu quero é através da tabela de dados que vou buscar ao servidor, numa folha de excel onde eu tenho uma tabela, queria fazer um PROCV para que este atualizasse sempre um campo, mas a questão é que dá sempre erro, mas caso eu vá na tabela onde tenho os dados importados e selecionar o campo que estou à procura no procv, e voltar à minha tabela ele assume o procv, mas depois caso feche e volte a abrir o ficheiro, continua com o erro… não sei se me fiz entender o que pretendo, mas desde já agradeço a ajuda.


Sql Server ODBC Linked Server

I’m trying to create a linked server in SQL server 2017, linked system is odbc (criteria criOdbc)

Test 1 Form SQL Server SSMS

select * from OPENROWSET('MSDASQL','DSN=criteria64;uid=xxxx;pwd=yyyy;','select * from table where key<10')

–> Give this error “Error converting data type DBTYPE_DBDATE to date.”

Test 2 Form SQL Server SSMS

select * from OPENROWSET('MSDASQL','DSN=criteria64;uid=xxxx;pwd=yyyy;','select key from table where key<10')

–> Works perfectly

Test 3 In c# (load form odbc then bulk insert in sql server)

OdbcConnection acc = new OdbcConnection("DSN=criteria64;uid=xxxx;pwd=yyyy;")
OdbcCommand cmd = new OdbcCommand("select * from table where key<10", acc);

–> Works perfectly

Test 4 connect the same table in MS Access as linked table

–> Works perfectly


  • Msdasql (Provider OLE DB Microsoft for ODBC) –> Doesn’t work well with date and some other type .net
  • System.Data.Odbc (.NET Framework
    Data Provider for ODBC) –> Works perfectly

Final question

Is possible to use NET Framework Data Provider for ODBC in linked server? (cant find any documentation)

If not

Is there any kind of connector (odbc based) tath I can try to use in linked server in alternative to “msdasql” ?

Thank you for your time

What is MS Access ODBC SQL syntax for a table with AutoIncrement and Memo columns?

I am migrating a full framework .NET app to core. It used ADOX to create an MS Access database and tables. It used OLE DB to populate data. In ADOX, the data type was ADOX.DataTypeEnum.adInteger and the syntax from c# was:

fld.Properties("Autoincrement").Value = true;
fld.Properties("Seed").Value = 1;
fld.Properties("Increment").Value = 1;

For memo, ADOX data type was ADOX.DataTypeEnum.adLongVarWChar.

Since we can no longer use ADOX under .NET Core, I have to use SQL DML through ODBC. When I attempt to create a table using syntax similar to

create table t (
  col1 int not null identity(1,1),
  col2 varchar(512)

I get a syntax error. When I try to adjust this for Access according to this and other related articles in the same documentation tree, I also get syntax error.

create table t (
  col1 counter,
  col2 text

What is the correct syntax for these columns that is compatible with .NET Core and MS Access ODBC driver?

MySQL Client out of memory when running a simple select query from MSSQL ODBC

Table has a total of 120,000 rows and 20 columns. When I run a select query on mysql directly like:

select * from <tablename> where UpdatedOn > '2020-10-05'

it gives the results which is about 50+ rows.

But when I run the same from MSSQL using ODBC Connection it throws “MySQL Client Out of Memory” every single time.

  • The server has 8 GB RAM and no one else is using the server
  • Running Select top gives the results without the error
  • Running select with a single integer column like select id from … throws a “MySQL Client out of memory”

What could be going wrong? I haven’t been able to the issue.

mysql – SSIS Error – ODBC Source

I am using ODBC connection to connect to MYSQL in SSIS – the connection is successful, but when the SSIS package is executed, I get the below error.

(ODBC Source (30)) Error: SQLSTATE: 22018, Message: (MySQL)(ODBC 8.0(a) Driver)(mysqld-5.7.30-0ubuntu0.16.04.1); (ODBC Source (30)) Error: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "ODBC Source.Outputs(ODBC Source Output)" failed because error code 0xC020F450 occurred, and the error row disposition on "ODBC Source" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure.

(SSIS.Pipeline) Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on ODBC Source returned error code 0xC0209029. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

Thanks in advance.

linux – Not able to find odbc driver for db2 10.5

There seems to be a problem like the DBA has lost the ODBC manager folder in the OS, either during migrating DB2 to 10.5 or deploying the application new code on last Saturday, now they can not see the ODBC manager folder of any version, so even if we revert it back the ODBC manager is needed on this OS ( linux SUSE 11). As a DBA confused what to look for, and what approach do i need to take??

sql server – ODBC XML Mapping

i am trying to map a GE Proficy Historian ODBC Collector but I am unsure as to how i would go about mapping the following sections.

my database has a column ‘tagname’ under which lies the pressure/temperature parameters i am saving into the database, and also columns for ‘timestamp’ and ‘datavalue’.

According to the XML mapping file that comes installed with the collector, there should be a quality tag(indicated by the ???? below) that cannot be left empty but i don’t have any such column, what should i populate there?


    <DBName>mydb</DBName> <!--Cannot be *NA*-->
    <TableName>DataLogger</TableName> <!--Cannot be *NA*-->
    <TagName>Temp</TagName> <!--Cannot be *NA*-->
    <Description>Temperature</Description> <!--If not applicable mark it as       "*NA*"-->
    <EngineeringUnits>*NA*</EngineeringUnits> <!--If not applicable mark it as "*NA*"-->
    <DataType>float</DataType>    <!--If not applicable mark it as "*NA*", However, when DataType is *NA*, Only one data type mapping can be done in <DataTypeMapping> section and all the rest shall be marked as *NA*-->
    <MinimumEngineeringUnit>*NA*</MinimumEngineeringUnit><!--If not applicable mark it as "*NA*"-->
    <MaximumEngineeringUnit>*NA*</MaximumEngineeringUnit><!--If not applicable mark it as "*NA*"-->

    <DBName>mydb</DBName> <!--Cannot be *NA*-->
    <TableName>DataLogger</TableName> <!--Cannot be *NA*--> 
    <TagName>tagname</TagName> <!--Cannot be *NA*-->
    <Timestamp>time_stamp</Timestamp> <!--Cannot be *NA*-->
    <Value>datavalue</Value> <!--Cannot be *NA*-->
    <Quality>?????</Quality> <!--Cannot be *NA*-->
    <SubQuality>*NA*</SubQuality> <!--If not applicable mark it as "*NA*"-->


Can someone shed some light as to whether or not i populated the fields correctly? Apologies if this is an amateur-ish question, I am very new to this.

Any help would be greatly appreciated, thank you very much in advance!