Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts

Friday, March 30, 2012

Runtime Error 3146 ODBC--Call Failed

Hi
I am using MSAccess 97, SQL Server 6.5 and VB.
While I am running reports I am getting the Following error.
Runtime Error '3146'
ODBC--Call Failed
Can anyonre please help me to solve this problem
Cheers
RaviCan you post you db connection code ?

Best regards
Mirador.

Wednesday, March 21, 2012

Running SSIS package from asp.net application failed

I have an asp.net web application and a web service (both of them are created in VS 2005 - asp.net 2.0). They are located on the same web server. In both web.config files, I have set <authentication mode="Windows"/> and <identity impersonate="true"/>. Also, configured the IIS settings to use Integrated Windows Authentication and unchecked the Anonymous access (for both). The web service is called from the web app, so I have to pass credentials for authentication to the web service. The web service loads and executes a SSIS package. The package and all the other sql objects are located in the sql server 2005 (windows server 2003 - the same server as the web server).

When run the web service from develop environment (vs. 2005), I get whatever I expected. When call it from web application, however, the package failed (no error message).

In the SSIS package, there are three connection managers –

· A: Microsoft OLE DB Provider for Analysis Services 9.0 à connectionType=OleDbConnection

· B: .Net Providers \ SqlClient Data Provider à connection type=SqlConnection

· C: Native OLE DB \ Microsoft OLE DB Provider for SQL Server à connectionType=OLEDB

After ran the web application and check the sql database, I can tell that the package was reached and when through the first two steps (clear some records in table_1 and extract some records from table_2 ) which relate to the connection manager B – ADO.Net connection. The remaining steps failed which are related to the connection managers A & C.

From SSIS package log file, found that the user credentials (domain and username) were correctly passed from web service to sql server 2005 at the first two events, but the credentials (or operator) changed from domainABC\user123 to NT AUTHORITY\NETWORK SERVICE after packageStart. Then, it complains … either the user, domainABC\serverName$, does not have access to the database, or the database does not exist.

I think the credentials are passed ok but some setting related to the Analysis services are not correct - complaining start from there. Any clues?

Please help and thank you all!

FYI: The problem was solved.

What I did are list as below:

A. We created a new web app pool and pointed the both web application and web service to this web app pool (which was configured not use default identity - Predefined: Network Service but use Configurable - created a new use name).

B. Under SQL server , added this new user and assign the certain rights to it.

C. In the web application and web service, set impersonate=false (instead of true)

D. In the SSIS package, we also have a flat file destination connection which is to write the output to .txt file. I give the read & write rights to this new use. then, it works.

running sql2005 job

hi, I have a job failed for the following error. The job is send an email to
me(outlook). any ideas?
Thanks
Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
component is turned off as part of the security configuration for this
server. A system administrator can enable the use of 'Ole Automation
Procedures' by using sp_configure. For more information about enabling 'Ole
Automation Procedures', see "Surface Area Configuration" in SQL Server Books
Online. [SQLSTATE 42000] (Error 15281). The step failed.mecn,
Yes, the idea is to do what the messages says: "enable the use of 'Ole
Automation
Procedures' by using sp_configure."
sp_configure 'Ole Automation Procedures', 1
GO
RECONFIGURE WITH OVERRIDE
GO
Or use the Surface Area Configuration tool to do the same thing
interactively.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
> hi, I have a job failed for the following error. The job is send an email
> to me(outlook). any ideas?
> Thanks
> Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
> 'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
> component is turned off as part of the security configuration for this
> server. A system administrator can enable the use of 'Ole Automation
> Procedures' by using sp_configure. For more information about enabling
> 'Ole Automation Procedures', see "Surface Area Configuration" in SQL
> Server Books Online. [SQLSTATE 42000] (Error 15281). The step failed.
>|||Thanks a lot. I apprecite
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%23eAfSXeqHHA.4548@.TK2MSFTNGP03.phx.gbl...
> mecn,
> Yes, the idea is to do what the messages says: "enable the use of 'Ole
> Automation
> Procedures' by using sp_configure."
> sp_configure 'Ole Automation Procedures', 1
> GO
> RECONFIGURE WITH OVERRIDE
> GO
> Or use the Surface Area Configuration tool to do the same thing
> interactively.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
>

Tuesday, March 20, 2012

running sql2005 job

hi, I have a job failed for the following error. The job is send an email to
me(outlook). any ideas?
Thanks
Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
component is turned off as part of the security configuration for this
server. A system administrator can enable the use of 'Ole Automation
Procedures' by using sp_configure. For more information about enabling 'Ole
Automation Procedures', see "Surface Area Configuration" in SQL Server Books
Online. [SQLSTATE 42000] (Error 15281). The step failed.
mecn,
Yes, the idea is to do what the messages says: "enable the use of 'Ole
Automation
Procedures' by using sp_configure."
sp_configure 'Ole Automation Procedures', 1
GO
RECONFIGURE WITH OVERRIDE
GO
Or use the Surface Area Configuration tool to do the same thing
interactively.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
> hi, I have a job failed for the following error. The job is send an email
> to me(outlook). any ideas?
> Thanks
> Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
> 'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
> component is turned off as part of the security configuration for this
> server. A system administrator can enable the use of 'Ole Automation
> Procedures' by using sp_configure. For more information about enabling
> 'Ole Automation Procedures', see "Surface Area Configuration" in SQL
> Server Books Online. [SQLSTATE 42000] (Error 15281). The step failed.
>
|||Thanks a lot. I apprecite
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%23eAfSXeqHHA.4548@.TK2MSFTNGP03.phx.gbl...
> mecn,
> Yes, the idea is to do what the messages says: "enable the use of 'Ole
> Automation
> Procedures' by using sp_configure."
> sp_configure 'Ole Automation Procedures', 1
> GO
> RECONFIGURE WITH OVERRIDE
> GO
> Or use the Surface Area Configuration tool to do the same thing
> interactively.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
>

running sql2005 job

hi, I have a job failed for the following error. The job is send an email to
me(outlook). any ideas?
Thanks
Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
component is turned off as part of the security configuration for this
server. A system administrator can enable the use of 'Ole Automation
Procedures' by using sp_configure. For more information about enabling 'Ole
Automation Procedures', see "Surface Area Configuration" in SQL Server Books
Online. [SQLSTATE 42000] (Error 15281). The step failed.Thanks a lot. I apprecite
"Russell Fields" <russellfields@.nomail.com> wrote in message
news:%23eAfSXeqHHA.4548@.TK2MSFTNGP03.phx.gbl...
> mecn,
> Yes, the idea is to do what the messages says: "enable the use of 'Ole
> Automation
> Procedures' by using sp_configure."
> sp_configure 'Ole Automation Procedures', 1
> GO
> RECONFIGURE WITH OVERRIDE
> GO
> Or use the Surface Area Configuration tool to do the same thing
> interactively.
> RLF
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
>> hi, I have a job failed for the following error. The job is send an email
>> to me(outlook). any ideas?
>> Thanks
>> Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
>> 'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
>> component is turned off as part of the security configuration for this
>> server. A system administrator can enable the use of 'Ole Automation
>> Procedures' by using sp_configure. For more information about enabling
>> 'Ole Automation Procedures', see "Surface Area Configuration" in SQL
>> Server Books Online. [SQLSTATE 42000] (Error 15281). The step failed.
>|||mecn,
Yes, the idea is to do what the messages says: "enable the use of 'Ole
Automation
Procedures' by using sp_configure."
sp_configure 'Ole Automation Procedures', 1
GO
RECONFIGURE WITH OVERRIDE
GO
Or use the Surface Area Configuration tool to do the same thing
interactively.
RLF
"mecn" <mecn2002@.yahoo.com> wrote in message
news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
> hi, I have a job failed for the following error. The job is send an email
> to me(outlook). any ideas?
> Thanks
> Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
> 'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
> component is turned off as part of the security configuration for this
> server. A system administrator can enable the use of 'Ole Automation
> Procedures' by using sp_configure. For more information about enabling
> 'Ole Automation Procedures', see "Surface Area Configuration" in SQL
> Server Books Online. [SQLSTATE 42000] (Error 15281). The step failed.
>|||I am having the same problem here.
I have enabled OLE Automation, the services are running under local system
account, but i am still not able to create an object using sp_OACreate
the error message i am getting is
0x80010105 ODSOLE Extended Procedure The server threw an exception.
It is very nice error message that it won't give any idea :)
Thanks
Joko
"mecn" wrote:
> Thanks a lot. I apprecite
>
> "Russell Fields" <russellfields@.nomail.com> wrote in message
> news:%23eAfSXeqHHA.4548@.TK2MSFTNGP03.phx.gbl...
> > mecn,
> >
> > Yes, the idea is to do what the messages says: "enable the use of 'Ole
> > Automation
> > Procedures' by using sp_configure."
> >
> > sp_configure 'Ole Automation Procedures', 1
> > GO
> > RECONFIGURE WITH OVERRIDE
> > GO
> >
> > Or use the Surface Area Configuration tool to do the same thing
> > interactively.
> >
> > RLF
> > "mecn" <mecn2002@.yahoo.com> wrote in message
> > news:uxeNiReqHHA.4224@.TK2MSFTNGP02.phx.gbl...
> >> hi, I have a job failed for the following error. The job is send an email
> >> to me(outlook). any ideas?
> >>
> >> Thanks
> >>
> >> Executed as user: GOEVO\SRVAdmin. SQL Server blocked access to procedure
> >> 'sys.sp_OACreate' of component 'Ole Automation Procedures' because this
> >> component is turned off as part of the security configuration for this
> >> server. A system administrator can enable the use of 'Ole Automation
> >> Procedures' by using sp_configure. For more information about enabling
> >> 'Ole Automation Procedures', see "Surface Area Configuration" in SQL
> >> Server Books Online. [SQLSTATE 42000] (Error 15281). The step failed.
> >>
> >
> >
>
>

running SQL 2005 under a user account cause servicefail to start

Hi,
I have changed the SQL Server account from local system to .\administrator
and then SQL Server failed to starts
the event log log 5 errors:
event ids: 17120, 17826, 17182, 17182, 26049
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
the Windows event logs for information about possible related problems.
Could not start the network library because of an internal error in the
network library. To determine the cause, review the errors immediately
preceding this one in the error log.
TDSSNIClient initialization failed with error 0x5, status code 0x1.
TDSSNIClient initialization failed with error 0x5, status code 0x40.
Server local connection provider failed to listen on [
\\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
my other services works fine under the administrator account (AS2005,
RS2005...)
any idea?
thanks.
Jerome.Hi
This looks like a permission thing, you may want to check the network
configuration. Have you tried removing named pipes?
John
"Jéjé" wrote:

> Hi,
> I have changed the SQL Server account from local system to .\administrator
> and then SQL Server failed to starts
> the event log log 5 errors:
> event ids: 17120, 17826, 17182, 17182, 26049
> SQL Server could not spawn FRunCM thread. Check the SQL Server error log a
nd
> the Windows event logs for information about possible related problems.
> Could not start the network library because of an internal error in the
> network library. To determine the cause, review the errors immediately
> preceding this one in the error log.
> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> Server local connection provider failed to listen on [
> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>
> my other services works fine under the administrator account (AS2005,
> RS2005...)
> any idea?
>
> thanks.
>
> Jerome.
>
>
>|||yes, no changes
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...[vbcol=seagreen]
> Hi
> This looks like a permission thing, you may want to check the network
> configuration. Have you tried removing named pipes?
> John
> "Jj" wrote:
>

Tuesday, February 21, 2012

running SQL 2005 under a user account cause servicefail to start

Hi,
I have changed the SQL Server account from local system to .\administrator
and then SQL Server failed to starts
the event log log 5 errors:
event ids: 17120, 17826, 17182, 17182, 26049
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
the Windows event logs for information about possible related problems.
Could not start the network library because of an internal error in the
network library. To determine the cause, review the errors immediately
preceding this one in the error log.
TDSSNIClient initialization failed with error 0x5, status code 0x1.
TDSSNIClient initialization failed with error 0x5, status code 0x40.
Server local connection provider failed to listen on [
\\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
my other services works fine under the administrator account (AS2005,
RS2005...)
any idea?
thanks.
Jerome.Hi
This looks like a permission thing, you may want to check the network
configuration. Have you tried removing named pipes?
John
"Jéjé" wrote:
> Hi,
> I have changed the SQL Server account from local system to .\administrator
> and then SQL Server failed to starts
> the event log log 5 errors:
> event ids: 17120, 17826, 17182, 17182, 26049
> SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
> the Windows event logs for information about possible related problems.
> Could not start the network library because of an internal error in the
> network library. To determine the cause, review the errors immediately
> preceding this one in the error log.
> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> Server local connection provider failed to listen on [
> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>
> my other services works fine under the administrator account (AS2005,
> RS2005...)
> any idea?
>
> thanks.
>
> Jerome.
>
>
>|||yes, no changes
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> Hi
> This looks like a permission thing, you may want to check the network
> configuration. Have you tried removing named pipes?
> John
> "Jéjé" wrote:
>> Hi,
>> I have changed the SQL Server account from local system to
>> .\administrator
>> and then SQL Server failed to starts
>> the event log log 5 errors:
>> event ids: 17120, 17826, 17182, 17182, 26049
>> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
>> and
>> the Windows event logs for information about possible related problems.
>> Could not start the network library because of an internal error in the
>> network library. To determine the cause, review the errors immediately
>> preceding this one in the error log.
>> TDSSNIClient initialization failed with error 0x5, status code 0x1.
>> TDSSNIClient initialization failed with error 0x5, status code 0x40.
>> Server local connection provider failed to listen on [
>> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>>
>> my other services works fine under the administrator account (AS2005,
>> RS2005...)
>> any idea?
>>
>> thanks.
>>
>> Jerome.
>>
>>|||Hi
I assume going back to local system still works? Have you tried a domain
account or a different local administrator?
John
"Jéjé" wrote:
> yes, no changes
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> > Hi
> >
> > This looks like a permission thing, you may want to check the network
> > configuration. Have you tried removing named pipes?
> >
> > John
> >
> > "Jéjé" wrote:
> >
> >> Hi,
> >>
> >> I have changed the SQL Server account from local system to
> >> .\administrator
> >> and then SQL Server failed to starts
> >> the event log log 5 errors:
> >> event ids: 17120, 17826, 17182, 17182, 26049
> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
> >> and
> >> the Windows event logs for information about possible related problems.
> >>
> >> Could not start the network library because of an internal error in the
> >> network library. To determine the cause, review the errors immediately
> >> preceding this one in the error log.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> >>
> >> Server local connection provider failed to listen on [
> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
> >>
> >>
> >>
> >> my other services works fine under the administrator account (AS2005,
> >> RS2005...)
> >>
> >> any idea?
> >>
> >>
> >>
> >> thanks.
> >>
> >>
> >>
> >> Jerome.
> >>
> >>
> >>
> >>
> >>
>
>|||Hi
Another thought! Have you tried changing the pipe name in SQL Server
Configuration Manager?
John
"Jéjé" wrote:
> yes, no changes
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
> > Hi
> >
> > This looks like a permission thing, you may want to check the network
> > configuration. Have you tried removing named pipes?
> >
> > John
> >
> > "Jéjé" wrote:
> >
> >> Hi,
> >>
> >> I have changed the SQL Server account from local system to
> >> .\administrator
> >> and then SQL Server failed to starts
> >> the event log log 5 errors:
> >> event ids: 17120, 17826, 17182, 17182, 26049
> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error log
> >> and
> >> the Windows event logs for information about possible related problems.
> >>
> >> Could not start the network library because of an internal error in the
> >> network library. To determine the cause, review the errors immediately
> >> preceding this one in the error log.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> >>
> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> >>
> >> Server local connection provider failed to listen on [
> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
> >>
> >>
> >>
> >> my other services works fine under the administrator account (AS2005,
> >> RS2005...)
> >>
> >> any idea?
> >>
> >>
> >>
> >> thanks.
> >>
> >>
> >>
> >> Jerome.
> >>
> >>
> >>
> >>
> >>
>
>|||finally its the solution, the named pipe protocol cause the error.
I disable it, and all works fine...
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BAC11602-9BC9-490B-868F-C2FDC9E3E1DE@.microsoft.com...
> Hi
> Another thought! Have you tried changing the pipe name in SQL Server
> Configuration Manager?
> John
> "Jéjé" wrote:
>> yes, no changes
>> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
>> news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...
>> > Hi
>> >
>> > This looks like a permission thing, you may want to check the network
>> > configuration. Have you tried removing named pipes?
>> >
>> > John
>> >
>> > "Jéjé" wrote:
>> >
>> >> Hi,
>> >>
>> >> I have changed the SQL Server account from local system to
>> >> .\administrator
>> >> and then SQL Server failed to starts
>> >> the event log log 5 errors:
>> >> event ids: 17120, 17826, 17182, 17182, 26049
>> >> SQL Server could not spawn FRunCM thread. Check the SQL Server error
>> >> log
>> >> and
>> >> the Windows event logs for information about possible related
>> >> problems.
>> >>
>> >> Could not start the network library because of an internal error in
>> >> the
>> >> network library. To determine the cause, review the errors immediately
>> >> preceding this one in the error log.
>> >>
>> >> TDSSNIClient initialization failed with error 0x5, status code 0x1.
>> >>
>> >> TDSSNIClient initialization failed with error 0x5, status code 0x40.
>> >>
>> >> Server local connection provider failed to listen on [
>> >> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>> >>
>> >>
>> >>
>> >> my other services works fine under the administrator account (AS2005,
>> >> RS2005...)
>> >>
>> >> any idea?
>> >>
>> >>
>> >>
>> >> thanks.
>> >>
>> >>
>> >>
>> >> Jerome.
>> >>
>> >>
>> >>
>> >>
>> >>
>>

running SQL 2005 under a user account cause servicefail to start

Hi,
I have changed the SQL Server account from local system to .\administrator
and then SQL Server failed to starts
the event log log 5 errors:
event ids: 17120, 17826, 17182, 17182, 26049
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
the Windows event logs for information about possible related problems.
Could not start the network library because of an internal error in the
network library. To determine the cause, review the errors immediately
preceding this one in the error log.
TDSSNIClient initialization failed with error 0x5, status code 0x1.
TDSSNIClient initialization failed with error 0x5, status code 0x40.
Server local connection provider failed to listen on [
\\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
my other services works fine under the administrator account (AS2005,
RS2005...)
any idea?
thanks.
Jerome.
Hi
This looks like a permission thing, you may want to check the network
configuration. Have you tried removing named pipes?
John
"Jéjé" wrote:

> Hi,
> I have changed the SQL Server account from local system to .\administrator
> and then SQL Server failed to starts
> the event log log 5 errors:
> event ids: 17120, 17826, 17182, 17182, 26049
> SQL Server could not spawn FRunCM thread. Check the SQL Server error log and
> the Windows event logs for information about possible related problems.
> Could not start the network library because of an internal error in the
> network library. To determine the cause, review the errors immediately
> preceding this one in the error log.
> TDSSNIClient initialization failed with error 0x5, status code 0x1.
> TDSSNIClient initialization failed with error 0x5, status code 0x40.
> Server local connection provider failed to listen on [
> \\.\pipe\SQLLocal\SQL2005 ]. Error: 0x5
>
> my other services works fine under the administrator account (AS2005,
> RS2005...)
> any idea?
>
> thanks.
>
> Jerome.
>
>
>
|||yes, no changes
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5A1CA870-06E8-4D43-A7E6-A715FD46281E@.microsoft.com...[vbcol=seagreen]
> Hi
> This looks like a permission thing, you may want to check the network
> configuration. Have you tried removing named pipes?
> John
> "Jj" wrote: