Showing posts with label encountered. Show all posts
Showing posts with label encountered. Show all posts

Tuesday, March 27, 2012

General network error

Hi guys,

Anyone encountered this error.

An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft OLE DB Provider for SQL Server" Hresult: 0x80004005 Description: "[DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation.".

The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the
component, but the error is fatal and the pipeline stopped executing.

Need your help...

thanks

I have the same error and we still do not have a solution. We have over 100 remote locations we are sending data to and just one of them this week started to give us this error. We are sending just 39 rows, all columns allow null values, nothing looks bad with the data. Can use ISQL to insert a row mannually, but using DTS or our ETL tool (with OLE DB) gives us the error.sql

Monday, March 26, 2012

garbage in sql server log files

hi,
My database server had hung up recently, and I had to restart it.
After checking the log I found some garbage entries in it.
has anyone encountered similar errors?
harshal.Garbage entry means what some of kind of ASCII characters or SQL DMP information?

Post a sample one here.|||Originally posted by Satya
Garbage entry means what some of kind of ASCII characters or SQL DMP information?

Post a sample one here.

There is some kind of ascii code|||What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?|||Originally posted by Satya
What is the level of service pack on SQL & OS?
What was the error related when it hung?
Any SQL.DMP files are created?

Error: 17883, Severity: 1, State: 0
The Scheduler 0 appears to be hung. SPID 94, ECID 0, UMS Context 0x39836B08.

sp3a and win 2k .|||Review information on following KBAs to deal with:
http://support.microsoft.com/?kbid=816840

http://support.microsoft.com/default.aspx?scid=kb;en-us;810885 - I feel this may be applicable to the situation if you use high-end subsystems h/w.

HTHsql

Friday, March 23, 2012

FYI - Performance Tuning Tip for SQL Server 2000 with Federated Model

We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters EXACTLY match the size of VARCHAR fields. If they don't, the procedures will run practically forever.
TIM ELLISON
This does not look right. Can you give an example?
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tim Ellison" <btesubscriptions@.direcway.com> wrote in message
news:OKaxTuHtFHA.3644@.TK2MSFTNGP11.phx.gbl...
We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters
EXACTLY match the size of VARCHAR fields. If they don't, the procedures
will run practically forever.
TIM ELLISON
|||Yes. I'm interested too!. Please post details.
Nik Marshall-Blank MCSD/MCDBA
"Tim Ellison" <btesubscriptions@.direcway.com> wrote in message news:OKaxTuHtFHA.3644@.TK2MSFTNGP11.phx.gbl...
We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters EXACTLY match the size of VARCHAR fields. If they don't, the procedures will run practically forever.
TIM ELLISON

FYI - Performance Tuning Tip for SQL Server 2000 with Federated Model

We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters EXACT
LY match the size of VARCHAR fields. If they don't, the procedures will run
practically forever.
--
TIM ELLISONThis does not look right. Can you give an example?
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tim Ellison" <btesubscriptions@.direcway.com> wrote in message
news:OKaxTuHtFHA.3644@.TK2MSFTNGP11.phx.gbl...
We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters
EXACTLY match the size of VARCHAR fields. If they don't, the procedures
will run practically forever.
TIM ELLISON|||Yes. I'm interested too!. Please post details.
--
Nik Marshall-Blank MCSD/MCDBA
"Tim Ellison" <btesubscriptions@.direcway.com> wrote in message news:OKaxTuHt
FHA.3644@.TK2MSFTNGP11.phx.gbl...
We just recently encountered this and I thought I'd pass it on.
If you are using SQL parameters for updates, make sure your parameters EXACT
LY match the size of VARCHAR fields. If they don't, the procedures will run
practically forever.
--
TIM ELLISONsql

Monday, March 19, 2012

Funny error during runs

Can any one please help explain why this error has happened, it is not a normal error of SSIS,

"SSIS Debug host has encountered a problem and needs to close. We are sorry for the inconvenience"

It has 2 buttons Debug and Close, this error happened in the middle of a script task.

This is a classic Microsoft problem. I face this problem often.

These are the scenarios on which I usually get this probelm:

1. If there is less memory on the client system where VB studio is open, and trying lot of mouse clicks frequently.

2. It is observed more when in Debug mode, when you try to scroll using the middle wheel of the mouse.

After I upgraded my desktop RAM to 3GB, and often system restart at the start of the day, I observed this error is less.

Also always saving and building frequently of the packages will help to retain your work. Other than these, there is no real solution from what I observed.