I have two 32-bit Windows Server 2003 R2, SP2 machines. I've tried using DebugDiag 1.2 to perform a performance-based dump of an IIS App Pool. I've tried this on both servers and they are coming up with a .dmp file that cannot be read by WinDBG/Visual Studio/DebugDiag.
I have been able to successfully create a manual .dmp file in the past using Adplus.vbs from the command line.
When using dumpchk.exe I get this message:
C:\debugging\server>"c:\Program Files (x86)\Debugging Tools for Windows (x86)\dumpchk.exe" w3wp.exe_HTTPRESPONSE_RULE1.dmp
Loading dump file w3wp.exe_HTTPRESPONSE_RULE1.dmp
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\debugging\server\w3wp.exe_HTTPRESPONSE_RULE1.dmp]
Minidump does not have system info
Could not open dump file [w3wp.exe_HTTPRESPONSE_RULE1.dmp], HRESULT 0x80004005
"Unspecified error"
**** DebugClient cannot open DumpFile - error 80004005
Has anyone else run across something like this?
Related
Problem: Hi SO community. Trying to execute a VS_2019 package that I can execute while in BIDS. Ran though all the specs including converting the package to
1) Package deployment mode
2) Converted the package to run in 32-bit mode
3) Finally, creating a config file to store the Oracle server credentials in
using this url: https://www.sqlservercentral.com/articles/how-to-execute-an-ssis-package-from-the-command-line-or-a-batch-file
4) Build the project no issues ; i.e. zero erros.
What I have tried:
"C:\Program Files (x86)\Microsoft SQL Server\150\DTS\Binn\DTExec.exe" /file "C:\Users\name\Desktop\SSIS_Local\JDA_Test\bin\Development\OrderAccuracy.dtsx" /config "C:\Users\name\Desktop\SSIS_Local\JDA_Test\JDA_PackageDeployment_Config.dtsConfig"
AND
"C:\Program Files\Microsoft SQL Server\150\DTS\Binn\DTExec.exe" /file "C:\Users\name\Desktop\SSIS_Local\JDA_Test\bin\Development\OrderAccuracy.dtsx" /config "C:\Users\name\Desktop\SSIS_Local\JDA_Test\JDA_PackageDeployment_Config.dtsConfig"
and both give me the error: The SSIS runtime version 15.0.2000.5 is too low for this Oracle connector. Please install a newer version of SSIS (later than SQL Server 2019 RTM).
End Error
Finally: internals of config file are:
SERVER=0.0.025.183:1521/DB;USERNAME=PB;WINAUTH=0;data source=0.0.225.183:1521/db;user id=pb;password=kuttp8x2bRRE;
So any help or direction would be great. Please feel free to ask any further questions.
I'm NOT even connecting to a SQL Server 2019. My source is Oracle. And my destination is going to be a flat file. This data will go into Snowflake database. But ETL tool used to connect to Oracle is SSIS.
Solution was to install the latest SQL Server 2019 update located here:
https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4548597%2Fcumulative-update-4-for-sql-server-2019&data=02%7C01%7Cv-sagkal%40microsoft.com%7C69a0e5d79ceb4ae3e20608d7daec4509%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637218580624686059&sdata=4avejidj69V2tJoQ5CWAaqIX9SCaHohWD%2F4we5hEGsg%3D&reserved=0
Package now runs with both 32-bit and 64-bit DTSExec versions. Password for source is stored in a config file and solution is on 'package deployment mode' .
Solution for anyone who runs into this issue in future.
I have a SQL*Loader Control File on my computer.
The input data file on the server is C:\data\myfile.csv.
In ctl file I add INFILE 'C:\data\myfile.csv'.
I have run with command:
sqlldr admin/admin#//192.10.1.1:1521/orcl control=myctlfile.ctl
The log file:
SQL*Loader: Release 11.2.0.1.0 - Production on Tue Sep 18 16:09:00
2018 Copyright (c) 1982, 2009, Oracle and/or its affiliates.
All rights reserved.
SQL*Loader-500: Unable to open file (C:\data\myfile.csv)
SQL*Loader-553: file not found
SQL*Loader-509: System error: The system cannot find the file specified.
When I move file C:\data\myfile.csv from server to my computer it works fine.
I want to use a file on the server. Is this feasibile?
SQL*Loader is a client application. It needs to be able to open the file, otherwise it can't load it.
If the file is on a remote server, you might look at network folder sharing (Windows public folder sharing, SkyDrive, Samba etc) to make the remote file accessible from your desktop.
Hope things going good.
I want to connect two windows server using ssh.But, My problem is, when I use the ANT task 'sshexec' to execute a .bat file from a remote WINDOWS server 2009 like this:
<sshexec host="10.46.220.108"
username="support"
password="India123"
trust="true"
verbose="true"
command="D:\project\jboss-eap-6.1\bin\standalone.bat -b hostname41" />
My execution gets hanged and stops with the below lines.
[sshexec] Connecting to hostname:22
[sshexec] cmd :D:\project\jboss-eap-6.1\bin\standalone.bat -b hostname41
[sshexec] Microsoft Windows [Version 6.1.7601]
[sshexec] Copyright (c) 2009 Microsoft Corporation. All rights reserved.
[sshexec] C:\users\administrator>
Guide me to resolve this.
NOTE: The remote server is running copssh in port number 22
How can I check all oracle versions and platforms that installed on windows machine from a command line or byscript ?
Till now I was using tnsping and check for the output but it only show the first version according to the path environment variable.
Is there a way to get this info from the registry and without actually connect to DB ?
Simplest method is to run command prompt and type sqlplus
it will show you the oracle version without actually logging into it.
Example: Run -> cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\xyz>sqlplus
SQL*Plus: Release 11.2.0.1.0 Production on Wed Jan 1 16:46:40 2014
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Enter user-name:
You'll want to query the Oracle Inventory.
For every Oracle installation, there is an entry in the "Oracle inventory". By default, the Oracle inventory is located under "C:\Program Files\Oracle\Inventory". However, this location can be changed.
In the Registry, the location of the Oracle inventory is in "HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE", where you'll find the key "inst_loc". There, you'll find an XML file containing all installed versions (inventory.xml). See the Oracle documentation for an example.
Go here and open with Notepad:
C:\Program Files (x86)\Oracle\Inventory\ContentsXML
C:\Program Files\Oracle\Inventory\ContentsXML
Open File:
inventory.xml
<?xml version="1.0" standalone="yes" ?>
<!-- Copyright (c) 1999, 2006, Oracle. All rights reserved. -->
<!-- Do not modify the contents of this file by hand. -->
<INVENTORY>
<VERSION_INFO>
<SAVED_WITH>11.1.0.6.0</SAVED_WITH>
<MINIMUM_VER>2.1.0.6.0</MINIMUM_VER>
</VERSION_INFO>
<HOME_LIST>
<HOME NAME="OraClient11g_home1" LOC="D:\Oracle\product\11.1.0\client_1" TYPE="O" IDX="1"/>
</HOME_LIST>
</INVENTORY>
Using SSMS I created an export a query to Excel and saved it as a DTSX package. Imported this DTSX package into a BIDS project to make it run hourly and export a excel file with timestamp appended to it, dynamic name using expressions. When I run from BIDS, package executes successfully and creates the excel file without a problem. I have enabled DelayedValidation flag.
I can double click on the DTSX file, run the package and it creates the excel file without a problem. When I configure as a SQL Job, it fails with the below error
Any guidance is much appreciated
Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved.
Started: 2:53:03 PM
Error: 2012-09-21 14:53:05.54
Code: 0xC0202009
Source: Export MyExportQuery to Excel Destination - Query [73]
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E37. End Error
Error: 2012-09-21 14:53:05.54
Code: 0xC02020E8
Source: Export MyExportQuery to Excel Destination - Query [73]
Description: Opening a rowset for "Query" failed. Check that the object exists in the database. End Error
Error: 2012-09-21 14:53:05.54
Code: 0xC004701A
Source: Export MyExportQuery to Excel SSIS.Pipeline
Description: component "Destination - Query" (73) failed the pre-execute phase and returned error code 0xC02020E8. End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 2:53:03 PM
Finished: 2:53:05 PM
Elapsed: 2.282 seconds. The package execution failed. The step failed.
EDIT:
SSIS is configured to run in 32 bit mode
Most of the problems arise due to these situations:
Data source connection or File access issue (when the user running the sql agent doesn't have the right permissions to the db or to the destination file).
Package protection level (pwd are sensitive data, and sometimes are not copied depending on the protection level).
64bit issue (this a common one on XL exports. Since there's no Jet Driver for 64bit systems, when running on a 64bit OS you need to either use the 32bit DTEXEC in your sql job or set the "Use 32bit runtime" option, it's on the "Execution options" tab when you're creating a SSIS job step, check the image on link below for seeing it).
32Bit runtime option image
For information on this topic, have a look at this article, it has detailed information on situations when ssis packages run on BIDS but not on SQL jobs..
How do I troubleshoot SSIS packages failed execution in a SQL Agent job?
Hope this helps you..
Kind regards,
When you configure a SQL Server Agent job with a job step type of SQL Server Integration Services Package, the job invokes the dtexec utility. However, the version of the dtexec utility that the job invokes depends on what versions of SQL Server and SQL Server Agent have been installed and are running on the 64-bit computer. [MSDN]
To run a package in 32-bit mode from a 64-bit version of SQL Server Agent, select Use 32 bit runtime on the Execution options tab of the New Job Step dialog box.