Someone scheduled a task on Windows 2008 R2 which runs in the midnight.It Runs some Java program or Probably Visual Basic EXE to pull data from a different FTP to local server.
I am a programmer.
When I go to the task scheduler i don't see that task running i spent many hours on to figure it out which exe is being called and where that EXE is but did not help.
I checked in event viewer and the only this is what i see, so how do i find which exe is being called off where the event is and what time its scheduled
You need to go to the "Task Scheduler Library", click on the task in question, then go to the actions tab, which will show what is happening and what parameters. In your case the "meat" of what is happening is probably parameters passed to cmd.exe.
I've used Windows Task Scheduler for 3 years now and never used "Running Tasks".
EDIT: This is from Windows 7, but I believe Windows Server 2008 has the same Task Scheduler/UI.
Related
We ran in the following problem in our system.
We have several reports, built with Stimulsoft. Reports use SQL Server as datasource (instead of stored procedures, SQL code is provided inside scripts).
When we run sql scripts in management studio - each of them runs in 3-5 sec. When then stimulsoft builds report, it takes 20 seconds. That's fine - because reports are cross-tab reports, and it is supposed to be a lot of calculations.
We use Windows server 2008 R2 64-bit. IIS process w3wp.exe runs in 32-bit mode. When we run 10 different reports, each of them increase memory usage of w3wp.exe by 300-400 M. And when it reaches almost 2Gb, the following reports stop to execute.
Any idea how to say w3wp to run as 64-bit process?
Launch IIS Manager and select the Application Pools node. Right click on the specific application pool that your site/application resides in and select "Advanced Settings". There'll be a setting under "General" labelled "Enabled 32-Bit Applications":
Set this value to "True" for to run w3wp.exe as a 32 bit process or "False" to run as a 64 bit process.
I am doing PHP development in Visual Studio, and my solution contains projects for PHP, SSRS, and SQL Server (SSDT). And I am using TFS for version control. So there's a lot going on in my dev environment that can "go wrong".
I am experiencing intermittent hangs, usually around 5 minutes a clip. Visual Studio gives me the wait cursor, and if I click anywhere in VS the window dims. And then I just have to wait it out. Sometimes I can end the devenv.exe task, other times it takes several minutes to terminate the task. If I am feeling patient, I just wait and eventually (around 5 mins) VS comes back to life. I've never experienced loss of data, source control issues, etc, even when I terminate the process.
It happens sometimes when I save. Sometimes when I check-in. Sometimes when I check out. Sometimes when I build. I have been unable to discern any sort of pattern of the behavior.
All my workstation resources are fine- no RAM or i/o or network or CPU issues.
What can I do to troubleshoot this issue? Can I run VS in some sort of logging mode that would allow me to pinpoint what is taking so long during these periods of lockup?
To turn on logging in visual studio, run: devenv.exe /log
I personally would do this with a shortcut.
Consider deleting old TFS Workspace definitions left over from Continuous Integration Builds.
We had this same problem with a large Team Foundation Server project tree.
Sometimes, but not always, opening a Solution in Visual Studio 2010 or Visual Studio 2012 would hang exactly as described above. VS 2010 was most vulnerable; VS 2012 seemed less vulnerable, but it still would hang.
We were able to get some clues by monitoring the server activity on the TFS Server machine and the underlying SQL Server machine. A certain query stored procedure was using excessive CPU time in SQL Server. We tracked this stored procedure name to a TFS operation involved in scanning TFS Workspace definitions for other user's checkouts for files.
Our TFS environment has been in use for over 3 years, and we have been using Continuous Integration build definitions using a "zombie army" of developer workstations as TFS Build Agent hosts. We also create new TFS Branches for major releases. Each branch contains about 20 separate Visual Studio Solutions with their own build definitions.
Over time, we had accumulated about 2,000 TFS Workspace definitions on each developer workstation. We had about 10 workstations at one time with their own definitions.
Using the Visual Studio Command window and running as a TFS Administrator, we used this command to identify all workspaces created by our "build user":
tf workspaces /collection:tfservername\collectionname /owner:ourbuilduser >c:\tf_ws_del.bat
We then used global substitutes and the Notepad++ editor macro recorder to convert each result line into this form:
tf workspace /delete /collection:tfservername\collectionname workspacename;ourbuilduser <c:\yes.txt
where C:\yes.txt contained a single line of "y"
We also used some human judgement to remove deletion lines for workspaces named for our most recent TFS branch.
We then ran that c:\tfs_ws_del.bat script in the same Visual Studio Command window and waited patiently for it to finish.
End Result: Our Visual Studio solutions open very quickly. Even browsing the folder hierarchy in Source Control Explorer has sped up considerably.
WARNING: The deletion operations for a very large number of workspaces may expand the TempDB on the underlying SQL Server by a large amount. Coordinate with your DBA's to monitor space on the SQL Server machine. Stopping and restarting the TFS Collection via the graphical TFS Administrator Console tool helps reclaim some of that TempDB space and return it to its internal "free block" list.
This can also seem to happen when the symbol servers specified in your debug options are down or unreachable... it will not actually hang in this case but seem to as it times out for each file access.
To temporarily get around this problem uncheck the symbol servers that are down.
I am having trouble getting builds to complete when they are set to run Dotfuscator on files. My environment is Visual Studio Professional 2012 paired with Team Foundation Server 2012, thus I am using Build Definitions and the Microsoft Team Foundation build architecture (build controller, build agents, etc).
My problem is that when I launch a build definition in Release config, which is set to run Dotfuscator Professional on my output files, the build hangs (either that or runs for so long that I have yet to see one complete). The log file shows that it is hanging during the build process template activity "Associate Changesets and Work Items", and task manager on my build server confirms that at this point Dotfuscator is running with huge CPU and memory requirements (around 50% CPU and I've seen near a gig of memory required). Here is the latter portion of the build log...
Find Property Values
CurrentLabel =
LastLabel =
Result = (Collection)
UpdateWorkItems = True
Final Property Values
Condition = True
Final Property Values
Condition = True
The last lines are duplicated on purpose, this is exactly what the log reads. This is where the build hangs and Dotfuscator is still running on the build server.
And here's the interesting part, when I do a local build on the build server (right click on solution, click rebuild) the build runs great, done in under a minute Dotfuscator and all. This suggests to me that something is going on between Dotfuscator and Team Foundation Build. Possibly something to do with the Build Process Template and/or Build Agents? I'm not much of an expert on Team Foundation Build other than the work I have done getting to this point.
Any ideas on what I can do to get Dotfuscator to run faster or correctly (depending on the cause of my error)? All help is much appreciated.
sprintf_s(cmd, "%c:\index.exe", driver);
I am trying to run a flash file, the application is built in VS 2008 , on win 7. The application works well on WIN7 but fails in XP. Ie the application launches but doesn't complete the task. I see the application running in Task Manager
I would hazard a guess that exitcode in your while loop is always non-zero so you're just going round an infinite loop.
This is a repost from the msdn forums that got no good results.
In VSeWSS 1.3 on VS 2008, the "Attach to IIS Worker Processes" seems to always be grayed out (Build -> Quick Deploy Solution).
This forces me to run iisapp from the command line, note the PID of my w3wp process, hit Ctrl-Alt-P in VS to bring up the Attach to Process dialog, sort by PID, locate the PID i obtained earlier, and hit ok.
What am I missing?
In order to get the "Attach to worker process" to not be grayed out, I have to select the project node in solution explorer. (This is the only project in this solution.) If I select a sub-folder or file the option is grayed out.
For some reason, I run into the same issue when I have multiple instances of w3wp running (which is obviously going to be the case if you are hosting Central Admin and your SSP in seperate app pools.) I recommend just closing all w3wp processes that aren't executing the code you are attempting to debug; close VS, reset IIS, open VS and try again.