Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to th
e
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'
Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'

Error 18456 - ODBC connection failed for domain user account

I have a user that her domain user account is failing to access a sql server
database while another persons domain account with the same permission to the
database works just fine. I remote into the workstation and test the odbc
connection with my user account and it worked just fine. Any help.
I am getting this message below
Connection failed Sql state 28000 error 18456 microsoft odbc connection
login failed for user bhcs/connie'Aboki,
This should be a straight-forward error that means: bhcs/connie has no right
to login on the server.
Check to be sure: the login is the proper one (not one spelled almost the
same), that connie was not denied login, etc.
RLF
"Aboki" <Aboki@.discussions.microsoft.com> wrote in message
news:4C4AD587-76B4-498F-9D1A-99ED809F7294@.microsoft.com...
>I have a user that her domain user account is failing to access a sql
>server
> database while another persons domain account with the same permission to
> the
> database works just fine. I remote into the workstation and test the odbc
> connection with my user account and it worked just fine. Any help.
> I am getting this message below
> Connection failed Sql state 28000 error 18456 microsoft odbc connection
> login failed for user bhcs/connie'sql

Error 0xC0047012 trying to import flat file in SSIS

I'm trying to do a simple flat file import of a .csv file. The task keeps failing on me and I get the following error

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039

I looked up the error codes and the only information I can find is that a thread is failing. What would cause this and how can I fix it? I can open the same file in Excel without any problems. I'd really appreciate any insight that anyone has to offer.

Does your package do anything else than importing the flat file?

Could you try nail down a piece of data in your file that is causing this? You can do it by splitting the file in two and keeping the failing part until you get the minimal amount of data causing this failure.

If your data is not sensitive I would like to do some testing with your file as well.

Thanks.

|||

Bob,

Thank you for the tip. I've been working on it all day and finally started coming to the same place you mentioned. I was finally able to get rid of the error by modifying the column data types in the Flat File connection.

Error : Difference of two datetime columns caused overflow at runtime.

At my job is a dts package that is failing in SQL 2005. I am not a SQL
expert. I am just trying to fix. I put the query in Query Analyzer
and get this error:

(4322 row(s) affected)

Server: Msg 535, Level 16, State 1, Line 1
Difference of two datetime columns caused overflow at runtime.

I am just trying to understand what this means, what I should be
looking for and what could be wrong. Here is the query:

SELECT i.SerialNumber, '' AS mac_number, DATEDIFF([second], 'Jan 1,
1970', s.DateOrdered) AS Support_StartDt, DATEDIFF([second], 'Jan 1,
1970',
s.Warranty_Enddate) AS Support_EndDt,
DATEDIFF([second], 'Jan 1, 1970', c.Registration_Date) AS
Registration_Date, c.FirstName AS enduser_fname,
c.LastName AS enduser_lname, c.CompanyName AS
enduser_companyname, c.ContactEmail AS enduser_email, c.Address AS
enduser_address1,
c.Address2 AS enduser_address2, c.City AS
enduser_city, c.State AS enduser_state, c.Zip AS enduser_zip,
c.WorkPhone AS enduser_phone,
c.Fax AS enduser_fax, d.DealerName AS
dealer_companyname, d.ContactFirstName AS dealer_fname,
d.ContactLastName AS dealer_name,
d.Address1 AS dealer_address, d.City AS
dealer_city, d.State AS dealer_state, d.Zip AS dealer_zip,
d.ContactPhone AS dealer_phone,
d.ContactFax AS dealer_fax,
ISNULL(SUBSTRING(p.ProductName, 11, LEN(p.ProductName) - 10), 'unknown
IWP product') AS product_type, '' AS extra1,
'' AS extra2, '' AS extra3, '' AS extra4, '' AS
extra5, '' AS extra6, '' AS extra7
FROM tblInventory i full outer JOIN
tblDealers d ON i.DealerID = d.DealerID full
OUTER JOIN
tblSupport s ON i.InventoryID = s.InventoryID
full outer JOIN
tblCustomers c ON s.InventoryID = c.InventoryID
LEFT OUTER JOIN
tblProducts p ON LEFT(i.SerialNumber,
PATINDEX('%-%', i.SerialNumber)) = p.SerialPrefix
WHERE i.SerialNumber <> ''

Any ideas would be greatly appreciated.geekwagon@.gmail.com (geekwagon@.gmail.com) writes:
> At my job is a dts package that is failing in SQL 2005. I am not a SQL
> expert. I am just trying to fix. I put the query in Query Analyzer
> and get this error:
>
> (4322 row(s) affected)
> Server: Msg 535, Level 16, State 1, Line 1
> Difference of two datetime columns caused overflow at runtime.
>
> I am just trying to understand what this means, what I should be
> looking for and what could be wrong. Here is the query:
>
> SELECT i.SerialNumber, '' AS mac_number, DATEDIFF([second], 'Jan 1,
> 1970', s.DateOrdered) AS Support_StartDt, DATEDIFF([second], 'Jan 1,
> 1970',
> s.Warranty_Enddate) AS Support_EndDt,
> DATEDIFF([second], 'Jan 1, 1970', c.Registration_Date) AS

One or of the rows has a value that is in 2038 or later in one of the
columns. My bets are on Warranty_Enddate and somehas put in 99991231
for an infinite warranty.

(2038-01-19 03:14:07.000 is the time when the number of seconds since
1970-01-01 exceeds the range of an un integer.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||>From Transact-SQL Reference:

DATEDIFF produces an error if the result is out of range for integer
values. For milliseconds, the maximum number is 24 days, 20 hours, 31
minutes and 23.647 seconds. For seconds, the maximum number is 68 years.

Error "merge process could not initialize publisher XXX"

Hello All-
We have a SQL Server 2000 Merge publication with about 10 push clients
running MSDE.
There are 2 subscribers that appear to be failing when connecting to the
publisher. The publisher & distributor are on the same host. If we look
at the Replication Monitor, the 'duration' column for these 2 clients have
a very small "Duration" value, usually under 1 minute. Other clients on
the same network are up for hours or days.
We have the agent schedule to start when SQL Server starts & also to start
every 1 minute. So, it appears these 2 subscribers are continuously failing
on connect.
In order to get more info, I changed the command line parameters ( in edit
job steps) to output details. The details are at the bottom of this message.
The details say another merge agent for this replication subscriber is
already running. I'm not sure what action to take on this error.
Any ideas?
Thanks,
bruce

[5/6/2004 8:25:56 AM]BASKINGRIDGE.CDB: set nocount on declare @.dbname
sysname select @.dbname = db_name() declare @.collation nvarchar(255) select
@.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Percent Complete: 1
Connecting to Publisher 'BASKINGRIDGE'
The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
Percent Complete: 0
The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147198719
Message: The merge process could not initialize the Publisher
'BASKINGRIDGE:CDB'.
Percent Complete: 0
Category:COMMAND
Source: Failed Command
Number: 0
Message: {call master..sp_MScheck_agent_instance
(N'BASKINGRIDGE-CDB-CDB-BABYLON-24', 4)}
Percent Complete: 0
Category:SQLSERVER
Source: BASKINGRIDGE
Number: 21036
Message: Another merge agent for the subscription(s) is running.
Disconnecting from Publisher 'BASKINGRIDGE'
Disconnecting from Distributor 'BASKINGRIDGE'
start task manager and verify that you have one merge.exe process in taskman
for each merge agent currently running on your system. If not, try to
selectively kill the rougue merge agent, and then start the new one.
"rr" <bruceradtke@.REMOVEspamREMOVE.earthlink.net> wrote in message
news:dTqmc.59231$Nn4.13413268@.twister.nyc.rr.com.. .
> Hello All-
> We have a SQL Server 2000 Merge publication with about 10 push clients
> running MSDE.
> There are 2 subscribers that appear to be failing when connecting to the
> publisher. The publisher & distributor are on the same host. If we look
> at the Replication Monitor, the 'duration' column for these 2 clients
have
> a very small "Duration" value, usually under 1 minute. Other clients on
> the same network are up for hours or days.
> We have the agent schedule to start when SQL Server starts & also to start
> every 1 minute. So, it appears these 2 subscribers are continuously
failing
> on connect.
> In order to get more info, I changed the command line parameters ( in edit
> job steps) to output details. The details are at the bottom of this
message.
> The details say another merge agent for this replication subscriber is
> already running. I'm not sure what action to take on this error.
> Any ideas?
> Thanks,
> bruce
>
> ----
> [5/6/2004 8:25:56 AM]BASKINGRIDGE.CDB: set nocount on declare @.dbname
> sysname select @.dbname = db_name() declare @.collation nvarchar(255) select
> @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
> N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
> 'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
> collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
> Percent Complete: 1
> Connecting to Publisher 'BASKINGRIDGE'
> The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> The merge process could not initialize the Publisher 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> Category:NULL
> Source: Merge Replication Provider
> Number: -2147198719
> Message: The merge process could not initialize the Publisher
> 'BASKINGRIDGE:CDB'.
> Percent Complete: 0
> Category:COMMAND
> Source: Failed Command
> Number: 0
> Message: {call master..sp_MScheck_agent_instance
> (N'BASKINGRIDGE-CDB-CDB-BABYLON-24', 4)}
> Percent Complete: 0
> Category:SQLSERVER
> Source: BASKINGRIDGE
> Number: 21036
> Message: Another merge agent for the subscription(s) is running.
> Disconnecting from Publisher 'BASKINGRIDGE'
> Disconnecting from Distributor 'BASKINGRIDGE'
>
>