i am relative new to node red, so i am not sure how to resolve this Problem. When I try to deploy a Postresql node, I get a "Error: certificate has expired" Message. I'm not sure if this is important but at User and Password, I used the respective Username and Password from Server i want to send the Data to.
Related
Context: I keep raising this error when I try to execute an SSRS Email or File Drop subscription - and I have no idea why. The empty string '' seems to imply I need to add some specific user information but I have no idea where.
I was able to send a test email through the Database Mail wizard in the management studio. I noticed in the SQL Server sysmail_event_log record for that event the last_mod_user was NTService\MSSQLSERVER. But the failed subscription execution attempts are showing up under the sa in the last_mod_user I suspect something is at play between this discrepancy but idk how to fix it.
The error description also reads:
The mail could not be sent to the recipients because of the mail
server failure. (Sending Mail using Account 4 (2022-04-22T17:41:01).
Exception Message: Cannot send mails to mail server. (The SMTP server
requires a secure connection or the client was not authenticated. The
server response was: 5.7.57 Client not authenticated to send mail.
[BN0P110CA0026.NAMP110.PROD.OUTLOOK.COM]). )
Questions: Can someone please assist?
Add the account to the Local Admin of the Machine to fix the Operation.Mail one
I've problem here, I've been trying to load data in my postgreSQL Database, by using
psql -h suggestedorder.postgres.database.azure.com -d remote_mydb -U dev_ext#suggestedorder -c "\copy planning.PRUEBA (CENTRO, ALMACEN, FECHA_CARGA) from 'C:\Users\geradiaz.MODELO\Desktop\Envase\Selección_Envase\Inputs\No_Seleccionado\PRUEBA.csv' with delimiter as ','
Somehow after type this sentence CMD ask for a password:
But when I try to enter my password it just doesn't work, I can't type anything, so I push enter and it shows the next message "Unable to connect to server: FATAL: SSL connection is required. Please specify SSL options and retry."
Do you know guys if there is any way to make it? or How can I specify SSL options without disable them in azure?
But when I try to enter my password it just doesn't work, I can't type anything,
You don't get any feedback as you enter your password. You just have to take it on faith that your keyboard is working.
so I push enter and it shows the next message "Unable to connect to server: FATAL: SSL connection is required. Please specify SSL options and retry."
Actually the next message you got was "password authentication failed". I guess because you panicked when you noticed you weren't getting feedback, and so you never finished typing the password. (Also, "Unable to connect to server" doesn't appear in your screenshot at all, just the SSL part does)
Once psql's attempt to connect over SSL failed due to the password issue, it decided to try again without SSL. But the server rejected this attempt, leading to the 2nd error message (I don't know what caused the exact wording of that error message, it is not a wording I have seen before). If you set PGSSLMODE=require, then it won't bother to make this 2nd attempt, leading to cleaner error output.
I have created an intranet site that is running fine locally but when running with IIS I am getting a SqlException (0x80131904): Login failed for user 'DOMAIN\username' message. Not sure if it matters or not but I am remotely connecting the server from a different location.
I was hesitant to post as I am quite new to programming and feared looking silly but I have searched for days and days looking for a way to fix this. I have checked Windows authentication over and over as well as windows authorization.
Note: When logging in for windows authentication, If I enter the incorrect user details, the window appears again, if user details correct I can access the site. I can then navigate my way around the site until a point required to access the database. Looking forward to a resolution. Currently pulling my hair out.
Can supply code if requried
I have a cube running on SSAS SQL Server 2012.
Every time I want to connect to a cube, or update data in files that contain it, I (and all the other users) get the "Transport Layer Error" message.
I click "OK" and am prompted to re enter my credentials. Usually it works after that (though sometimes it doesn't).
This becomes very annoying when I need to refresh a file that contains a dozen of cubes: I need to enter the credentials 12 times.
Sometimes it becomes impossible to connect to the cube, I get stuck in a Transport Layer Error infinite loop.
Important note: The server is on a different domain than the PC, I am connected to it through a VPN.
Is there any way to get rid of this?
You should do it like this to avoid problems again
Data tab... From Other Sources... From Analysis Services...
Type in a server name, username, and password... click next
choose your database and click next
Check "Always attempt to use this file to refresh data". And check "Save password in file". Click Yes when the prompt pops up.
Click finish.
That will save your username and password (in clear text) into the odc file. (Be aware of this for security purposes.)
And if that doesnt help, try to create a whole new excel workbook and readd connections to the cube.
I realised a few minutes ago , in my sql server log; there was an error:
SSPI handshake failed with error code 0x8009030c, state 14 while
establishing a connection with integrated security; the connection has
been closed. Reason: AcceptSecurityContext failed. The Windows error
code indicates the cause of failure. The logon attempt failed
[CLIENT: 222.186.61.15]
But i don't have an sqlclient ip 222.186.61.15
I research this ip and :
Continent: Asia
Country: China cn flag
State/Region: Jiangsu Sheng
City: Nanjing
Is my Sql Server under attack?:)
What is this?
Thanks for help.
Short answer; probably, but don't panic.
Someone tried to log onto your SQL server with invalid login credentials. If its coming from an IP that's totally out there, then it's probably not just someone mistyping their password. I wouldn't be overly worried about it, though. Its pretty common to see stuff like this every once in a while. Usually, its someone or some tool going through a list of SQL servers and trying common login credentials in hopes of getting lucky.
Just make sure you have solid login credentials, maybe update your firewall/IDS, and watch your logs to make sure that IP (or another weird one) logs in later.