Have installed filebeat service in windows, to collect logs files to elastic, but it does not read any files. And when i try to stop the services it hangs.
After you stop the filebeat service with Task Manager, you need to erase the lock file in folder C:\ProgramData\filebeat\ to make it to read the yml file at next start of the service.
Solution:
Check the filebeat.yml file. The JSON format is sensitive to spaces and other formats.
In this case there was a row:
ignore_older: ‘7d’
that made the filebeat service to stop.
It only supports minutes and hours, so you need to enter like this:
ignore_older: ‘168h’
The ignore_older: ‘168h’ function will check the timestamp of the file, and not read files that was created more than 7 days ago.
The filebeat.yml file is in folder C:\Program Files\Filebeat on windows.
Below a example of a filebeat.yml file for use with TM1 logs files – you need to add spaces in the beginning of every line to get it to work.
by Roger·Comments Off on An authentication problem is preventing the dataflow from being refreshed
Product:
Microsoft Power Bi dataflow
Issue:
Get a error on all dataflow, Error: An authentication problem is preventing the dataflow from being refreshed. Please have the owner of the dataflow sign out of Power BI and sign back in and try again.
or error message like {“code”:”DMTS_OAuthTokenRefreshFailedError”,”details”:[{“code”:”DM_ErrorDetailNameCode_UnderlyingErrorMessage”,”detail”:{“type”:1,”value”:”AADSTS135010: UserPrincipal doesn’t have the key ID configured} from the dataset that use the dataflow.
Can happen if you change you windows pincode login from microsoft, and use the same account to run the dataflow with.
Solution:
Go to the dataflow in your workspace in https://app.powerbi.com/
Go to settings
Click on data source credentials
Click on edit credentials
If the value is correct, click Sign in without a change.
Confirm the login question you will get, from you company.
Go to the workspace.
Try to refresh the dataflow again.
More information:
This error indicates that the cached credentials for the dataflow owner have expired, changed, or are no longer authorized to access the data source, causing a Power BI refresh failure. To resolve it, the owner must sign out of the Power BI service, clear browser cache, sign back in, and re-enter credentials in the dataflow settings.
Actionable Steps to Resolve:
Re-authenticate Dataflow Credentials: The dataflow owner should go to the Power BI Service, locate the dataflow, go to Settings > Data source credentials, and click “Edit credentials” to re-authenticate.
Sign Out/In: Sign out of app.powerbi.com completely, clear your browser cache/cookies, and sign back in to refresh token authentication.
Check Data Source: If using a Gateway, ensure the credentials in the gateway settings are valid.
Verify Permissions: Ensure the user who created the dataflow still has permissions to the underlying data sources (SQL, SharePoint, etc.).
Issue:
What anti-virus software should i use on my old laptop?
Suggested solution:
Windows Defender is good, but when there are no more updates, you can consider to use a separate Anti-Virus software product.
You have to yourself decide what to use (and if you need it) as the software market for anti-virus program is lucrative, program that was good for 10 years ago is maybe not the best today.
Consider:
Is the software easy to understand for me? Can i setup schedule scans in a easy way?
What is the price the second year? Most software will give you a 50% discount the first year. Check if you can get a family price for 3-5 computers. Review sites have often links to good offers.
Does the software take a lot of CPU when running or does it do the scan in the “cloud” ? Check more than one review to see if the program will slow down your PC.
Check more than one review of the software – most top teen listings are only trying to sell you a special anti-virus software where they get most money from.
Do you trust the company behind the program? Check WIKI pages about what country the software comes from.
As of January 2006, ZoneAlarm was reportedly[6] sending data to the company’s servers in a covert fashion. A developer dismissed allegations that ZoneAlarm was spying on its clients, saying that it was an issue related to software updates and that it would be fixed.[7]
In December 2007, a browser toolbar was shipped with ZoneAlarm as an opt-out, which was not well received.[8] This was removed in later versions of the software.
On September 2, 2010, the free version of ZoneAlarm started showing a “Global Virus Alert” popup as a scareware tactic to get users to switch to their paid security suite.[9] The popup was turned off by ZoneAlarm marketing team after an uproar from disgruntled users, many of whom uninstalled the software.[10][11]
These program have a free version (that you can test):
We tested the Bitdefender windows version on Windows 10.
We run a deep scan, and it found things in old TM1 files, version 2.1.5, Trojan.GenericKD is Windows-only malware, as far as I know, so it’s highly likely that these detection’s are false positives, as it looks like many anti-virus software can find them in different files.
If there where issues, this are solved now. IBM sends out updates regularly. We checked the latest version PAL 2.1.14, and there where no issues there.
(It looks like the Bit-defender can not scan ZIP files larger than 2 GB)
We upgrade Bitdefender to PLUS version in hope the firewall should be part of that deal.
But firewall was not part of the PLUS version. We got the VPN function, but you can not choose what country you will be using. We need to upgrade again to get firewall…
The company change the offering every year, so the package you have the first year may be something different the next year. If you stop your automatic subscription, then the bitdefender program stops working when the subscription ends. Malwarebytes have a different solution.
Passwords manager is better to use separate program like:
by Roger·Comments Off on The refresh token has expired due to inactivity
Product:
Microsoft Power BI service Issue:
When click on refresh for a dataset (sematic model) in https://app.powerbi.com/ you get a error like:
Data source error: {“error”:{“code”:”DMTS_OAuthTokenRefreshFailedError”,”pbi.error”:{“code”:”DMTS_OAuthTokenRefreshFailedError”,”details”:[{“code”:”DM_ErrorDetailNameCode_UnderlyingErrorMessage”,”detail”:{“type”:1,”value”:”AADSTS700082: The refresh token has expired due to inactivity. The token was issued on 2024-11-19T10:55:36.9381120Z and was inactive for 90.00:00:00.
Solution:
Wait and try again later or go into your PowerBI report and update all credentials to different data sources you have used in your report.
In the dataset – go to settings – take over as owner – go to data source credentials
click on edit the credentials and update with your account information. This should refresh the token.
This issue can happen when the OAuth refresh token used by Power BI Service to authenticate with the data source has expired. The error message shows that your token has been inactive for 90 days, which is the default expiration period for Azure Active Directory (AAD) refresh tokens.
Here are a few suggestions you can check:
Re-authenticate the Data Source in Power BI Service
Go to Power BI Service (app.powerbi.com).
Navigate to Settings > Manage Connections and Gateways.
Locate the data source for your dataset.
Click Edit Credentials and sign in again using your credentials.
Choose the correct authentication method (usually OAuth2 for Analysis Services).
Save and retry the refresh.
Check and Update Permissions
If your credentials were updated or your permissions changed, you may need to reassign them.
Ensure that your account has read permissions on the Analysis Services data source.
If your organization uses Conditional Access Policies, check with your IT team to ensure Power BI can maintain an active connection.
Remove and Reconnect the Dataset
If the issue persists, try removing the dataset from Power BI Service and republishing it from Power BI Desktop.
Ensure Your Token Doesn’t Expire Again
If you’re using service accounts, consider setting up a refresh schedule to keep the token active.
Work with your IT admin to adjust AAD token lifetime policies to extend the refresh token validity.
Try a Personal Gateway (If Applicable)
If you’re using a Personal Mode gateway, restarting or reinstalling it might help.
by Roger·Comments Off on Signature not valid in the specified time frame
Product:
Microsoft Azure Blob Storage
Issue:
When you run ETL script to send files to your BLOB storage you get a error like this:
HTTP Status Code: 403 HTTP Reason Phrase: Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.
Signature not valid in the specified time frame:
Possible Solution:
Please check if the SAS KEY you use in your script have expired.
Create a new SAS KEY and insert that in your script to upload files, to solve the issue.
A Shared Access Signature (SAS) token is a unique string of encrypted text that encapsulates all the necessary details needed to authenticate a shared signature to access Azure Storage services. It also determines which service and resource can be accessed, the permissions granted, and the validity period of the signature.
If we look at the specifics of these tokens, there are 3 types of SAS tokens: Account SAS, Service SAS, and User Delegation SAS. This blog walks through Account SAS tokens specifically, as this is the type of token used to access storage, which is a critical (if not the most critical) point of failure in data security.
Account SAS Tokens
SAS tokens are encrypted codes in the form of URIs (Uniform Resource Identifier) that grant specific access rights to one or more Azure Storage resources, such as Azure Blob Storage, Azure File Storage, and Azure Queue Storage. Compared to other tokens, this extensive access means it’s crucial to handle Account SAS carefully to prevent unauthorized data access.
sv: The storage service version.
ss: The signed services, in this case, blobs.
srt: The signed resource types, in this case, service (s), container (c), and object (o).
sp: The signed permissions, in this case, read (r).
se: The expiry time for the SAS token (2024-04-10T23:59:59Z).
st: The start time for the SAS token (2024-04-08T00:00:00Z).
spr: The signed protocol, in this case, HTTPS.
sig: The signature, which is a hashed value generated using your account key and the specified parameters.
by Roger·Comments Off on Cannot connect to database server.
Product:
Microsoft SQL server 2022
Issue:
When on the server try to login with a SQL account in SSMS you get a error:
TITLE: Connect to Server
ADDITIONAL INFORMATION:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 – The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver–2146893019-database-engine-error
The certificate chain was issued by an authority that is not trusted
Substring extract text in column konto from first position to where we find the – character, this position is given with charindex, and then we check if the result is empty. In case the string does not contain a -, then we get a empty value. Then we show the orginal value – otherwise we show the substring without all text after – in the field.