WD MS SQL - Refuses to login

Ask a Question
,
1

Hi,

Although I already import my data from WD logfiles into a MS SQL database that I created several years ago, I decided to revisit WD MS SQL to see if I could get it working again. However, all to no avail. No matter what combo of server name or user name combinations, it fails to connect to enable set up of the table using my selected fields.

My MS SQL instance is on the same PC as WD. SQL server name is DESKTOP-R88PM8F\TREVSPC, username is DESKTOP-R88PM8F\Trev (uses Windows Authentication), however running the MS SQL component and attempting to ‘connect’ (the only button available, all others are greyed out) i get:-
'login failed for user DESKTOP-R88PM8F\Trev followed by Error connection login failed for user user DESKTOP-R88PM8F\Trev

What on earth am i doing wrong ? As a Software Tester fro over 25years and someone who has created many databases over time, I cannot fathom what is going on with this.

Any ideas ?

regards

TrevP

sql set up.PNG
sql set up.PNG462×315 8.16 KB

sql set up2.PNG
sql set up2.PNG942×277 33 KB

login error.PNG
login error.PNG412×79 1.27 KB

2

Have you tried just Trev

3

Hi Brian,

As in just ‘Trev’ for username ? Yes I have

Just looked at SQL Server logs and it seems issue is that WD using SQL Authentication, where my instance is set up for Windows authentication only - see attached

I have an SQL Server instance and WD on my laptop and using an older build of WD, ie 10.37S72 , this connects successfully and creates a table. It is inserting data but its the same row of data and am getting an error:-
‘Conversion failed when converting date and/or time from character string’
and then after 5 or so rows of this, i get Dataset not in edit or insert mode with no further rows inserted

So, there seems to be a issue in WD MSSQL 2.5 as wants to use SQL Authentication constantly rather than Windows Authentication, but the earlier WD MSSQL 2.4 does use Windows Authentication ?

Is there a component/dll that I can use from the older version of WD that I can copy over to the the latest version of WD and see if that will at least connect to my MS SQL instance on my main PC ?

Trev

server error.PNG
server error.PNG1157×23 2.74 KB

4

but you can mix and match .exe programs
i.e use the older WD MSSQL with the latest version of WD

I dont remember changing the login but I will check

5

Cheers Brian, i will copy the 2.4 version to the latest version and see what happens

Trev

6

i just checked and the latest version does use windows login

7

Thanks for looking at that Brian, but it just shows something isn’t right somehwere.

As already posted, my SQL log clearly says ‘login failed - Reason: An attempt to login using SQL Authentication…’, when WD MSSQL 2.5 attempts to connect, whereas the older 2.4 version, which i copied to my main PC, connects successfully.

However, I still have issues with the older version on my PC as although it does connect and creates a table, it creates a table with a couple of fields that I do not want and do not have ticked. I get conversion errors reported in the WS MSSQL component and after a couple of rows, if that are inserted into the table, I get database not in insert or edit mode.

So as it stands, with me, WD MSSQL 2.5 will not work/connect as my sql log advises the login was using SQL authentication. But WD MSSQL 2.4 connects successfully.

Another 'issue is that the WD MYSQL component also opens up as well

I will re-install WD MSSQL 2.5 again, and see what happens.

As said no great issue for me as I already import the monthly log files to my own created tables using my own methods. It would just be nice if I could get this working as it is supposed to work, just as source where i can cross check data if needed.

regards

Trev

8
Another 'issue is that the WD MYSQL component also opens up as well
not sure that that means
9

See attached image

Also see other attachment showing login issues side by sied of wdmssql2.4 and 2.5

Trev

opening as well.PNG
opening as well.PNG941×716 141 KB

side by side.PNG
side by side.PNG959×848 137 KB

10

I will setup SQL server 2019 (express) and do some testing/investigating

11

Cheers Brian

12

try this update
http://www.weather-display.com/downloadfiles/wdmssql.zip
vers 2.6
and tick to use windows login
click on save
then restart the program

13

WD MSSQL 2.6

This now successfully connects when selecting ‘Use Windows Login’ - Thanks Brian.

However, a few observations.

Table is created, however, I deselected both ‘station_id ‘ and ‘date’ fields but these are still created along with another field ‘year’, even though this is not even in the field selection list ?

With the ‘time’ field being a datetime data type, this meets my requirements so I do not need the ‘date’ field and I also don’t require the ‘station_id’ field, hence why I deselected those.

I do not need the ‘year’ field either, but I cannot deselect it with it not being in the list. If you are making the both ‘station_id’ and ‘date’ fields mandatory, perhaps they should be ticked but greyed out/not editable ?

My weather station is an OS WMR928, but I do not use the main temperature sensor that comes with that, I have 3 extra temp/humidity sensors, (which are set on channels1,2,& 3 on the WMR928 console) and have set extra sensor 3 to be my main temperature sensor within WD. However in the field selection list, the WMR extra sensors start at 2, not 1, (?),ie,‘extra_temperature_sensor_2’.
To get my extra sensor 3 to be read into the tables, It seems I have to actually to select field ‘extra_temperature_sensor_4’, along with ‘extra_humidity_4’ , or should I be selecting ‘wmr968_extra_temperature’ and ‘wmr968_extra_humidity’ along with ‘wmr_extra_sensor_number’ and then select ‘extra_temperature_sensor_3’, along with ‘extra_humidity_3’ and that will actually report my extra sensor 3?

Rows are successfully being written to the table despite the following being reported with every row being written:-

‘Conversion failed when converting date and/or time from character string. Error inserting Conversion failed when converting date and/or time from character string.’

After just over an hour of writing rows every minute to the table, it stopped with the following error being reported in the WD MSSQL panel:-
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records
ERROR: Update failed. Found 0 records at time/date 17:58:09 30/01/2020
ERROR: Update failed. Found 0 records at time/date 17:58:11 30/01/2020
ERROR: Update failed. Found 0 records at time/date 17:58:13 30/01/2020
ERROR: Update failed. Found 0 records at time/date 17:58:14 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:35 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:35 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:35 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:36 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:36 30/01/2020
ERROR: Update failed. Found 0 records at time/date 18:00:36 30/01/2020
Update failed. Found 0 records
Update failed. Found 0 records
Update failed. Found 0 records

UPDATE:

restarted wd and after updating for a little over 2 hours, rows stopped being inserted again with the message

Update failed. Found 0 records
ERROR: Update failed. Found 0 records at time/date

regards

Trev