Blog
- Home
- Blog
SQL Error 50000 - Best method to fix
This article covers method to fix SQL Error 50000.
This SQL error happens in the process of installing SQL Server Management Studio on one of the client machines.
If you receive SQL Server 50000 error on a SQL Agent Job, you need to Quit the job reporting failure.
To fix this SQL error, you can try the following queries:
1. Enable the SQL Broker on the Site database:
USE master; GO ALTER DATABASE CM_PR1 SET ENABLE_BROKER GO2. SET the Site Database as trustworthy:
USE master;
GO ALTER DATABASE CM_PR1 SET TRUSTWORTHY ON GO3. SET the Database to honor the HONOR_BROKER_PRIORITY:
USE master; GO ALTER DATABASE CM_PR1 SET HONOR_BROKER_PRIORITY ON; GO
JFTP Bad response error in Joomla - Best Method to resolve
This article covers how to fix JFTP bad response error in Joomla for our customers.
When trying to install new extensions in Joomla, some users might come across some errors indicating a “Bad Response”, where the extensions are not successfully installed.
These errors include:
-JFTP::mkdir: Bad response-JFTP::chmod: Bad response-JFTP::store: Bad responseTo fix this error, You could try to change the chmod permission to 777 (755 the default chmod) of your configuration.php file, and also the corresponding directory recursively.
To do this, modify the configuration.php file.
Simply search for the FTP settings within this file and input the FTP login details in the following fields:
public $ftp_host = '';
public $ftp_port = ’21’;
public $ftp_user = ”;
public $ftp_pass = ”;
public $ftp_root = ”;
public $ftp_enable = ‘1’;
SQL Server Error 5009 – Different scenarios and fixes
This article covers how to fix SQL Server Error 5009 error which occurs while adding or removing a database file or extending the database file size.
To fix Microsoft SQL Server Error 5009 While Adding Database File:
1. Set the Operating system permission on the mentioned .ldf file to full permission for your login account and SQL Server service account.
2. Change the location to the path where you have enough permission to create or add database files.
Manage Scheduled Tasks with PowerShell - How to do it
This article covers how to use the PowerShell features to create scheduled tasks. The Get-ScheduledTask cmdlet gets the task definition object of a scheduled task that is registered on a computer. You can use PowerShell to create and manage scheduled tasks. Managing scheduled tasks with PowerShell is made possible with the use of the ScheduledTasks module that’s built-in to Windows.
With the PowerShell Scheduled Tasks module, setting up scheduled tasks using PowerShell commands is made possible. This module provides the opportunity and means to create and deploy scheduled tasks programmatically on the local and remote computers.
Important scheduled task component:
1. Action – the action that is executed by the scheduled task. An action is typically to run a program or a script. A scheduled task can have more than one actions.
2. Trigger – controls when the scheduled task runs. Triggers can be time-based, like, setting a schedule for daily or hourly recurrence. Triggers can also be activity-based, which runs a task based on detected activities like computer startup, a user logs in, or logged events.
3. Principal – controls the security context used to run the scheduled task. Among other things, a principal includes the user account and the required privilege used by the scheduled task.
4. Settings – is a set of options and conditions that controls how the scheduled task behavior. As an example, you can customize a task to get removed after a consecutive number of days that the task is unused.
To add a Trigger for a scheduled task using PowerShell:
The cmdlet to use for creating a trigger is the New-ScheduledTaskTrigger cmdlet.
The command below creates a trigger to run daily at 3 PM.
Copy and run the code in PowerShell:
# Create a new trigger (Daily at 3 AM)$taskTrigger = New-ScheduledTaskTrigger -Daily -At 3PM$tasktriggerThis will Create a Trigger (Daily at 3 AM)
Enable Windows Lock Screen after Inactivity via GPO - How to do it
This article covers how to Enable Windows Lock Screen on domain computers or servers using Group Policy. Locking the computer screen when the user is inactive (idle) is an important information security element.
The user may forget to lock his desktop (with the keyboard shortcut Win + L) when he needs to leave the workplace for a short time.
If any other employee or client who is nearby can access his data. The auto-lock screen policy will fix this flaw.
After some time of inactivity (idle), the user's desktop will be automatically locked, and the user will need to re-enter their domain password to return to the session.
To enable lock screen with group policy:
1. Create a new GPO then edit it and go to:
Computer Config>Policies>Windows Settings>Security Settings>Local Policies>Security Options.
2. Find Interactive logon: Machine inactivity limit .
3. Set that to whatever time you want and it will lock the PC after it hits that timer.
To change my lock screen wallpaper using group policy:
1. Run GPEDIT. MSC.
2. Go this path "Computer Configuration\Policies\Administrative Templates\Control Panel\Personalization".
3. Enable the GP "Force a specific default lock screen image".
4. Specify the path to the image file.
5. Click OK.
To Find Windows 10's Spotlight Lock Screen Pictures:
1. Click View in File Explorer.
2. Click Options.
3. Click the View tab.
4. Select "Show hidden files, folders and drives" and click Apply.
5. Go to This PC > Local Disk (C:) > Users > [YOUR USERNAME] > AppData > Local > Packages > Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy > LocalState > Assets.
SQL error 300 - Fix it Now
This article covers tips to resolve SQL error 300. The reason of the error is related with user permission on VIEW SERVER STATE. You can upgrade SQL Server Management studio with the same version like SQL Instance or higher.
Also, To mitigate this error, give the following GRANT and the error message will disappear:
USE master
GO
GRANT VIEW SERVER STATE TO "LoginName"
