Microsoft OLE DB Provider for Analysis Services error 80004005

Hello

I get the following error message in one of my ASP applications:
--------------------------
Microsoft OLE DB Provider for Analysis Services error '80004005'
Cannot connect to the server '172.16.103.14'. The server is either not started or too busy.
--------------------------
The IIS server is on a different machine to the MSOLAP server.

When I change the ASP code to point the 'localhost' it runs fine so Im fairly confident the necessary db conn libraries are installed on the IIS server.

There does not appear to be any traffic between the IIS/MSOLAP servers. Although all TCP ports are open. Interestingly, there are other pages on the same site that access a SQL Server resident on the MSOLAP servers & there are no issues.

Any assistance on this matter would be greatly appreciated. (I am a relative novice re: ASP/MSOLAP/IIS etc)Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG|||You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.|||Originally posted by sqlguy7777
Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG

Everything seems to be in order on this front. You will note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK.|||Originally posted by beyond cool
You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.

Everything seems to be in order on this front. Note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK...unless im missing something here....|||Howdy kalaa,

Can you confirm you can do these things :

(1) Ping the SQL box by name from the web server from a dos window on the web server e.g. ping <SQL_Server_name>. This will test if you have connectivity to the SQL box from the web server and more importantly confirm the SQL box is recognised in DNS.

(2) you have a valid SQL user ID set up on the SQL box, and that user ID has at least read access in the required database on the SQL box.
This is the user ID that the web application will use to talk to the SQL box.

Cheers,

SG

method call works from .Net form and not from SQL CLR - EnterpriseLibrary used

Hello

I created a wrapper class for a function, and exposed it through CLR. However, if I call this function form SQL it blows up but if I call directly from a test Windows Form the call works fine.

The blow up is related to EnterpriseLibrary.Data, where my Queue class uses that library to do all data access call ops

Here's my wrapper class:

namespace inlineCLRsql{

public static class Wrapper{

public static void CallQueueEntry(int queueId, int deskNo, int missed){

inLineLib.Queue oQueue;

inLineLib.QueueEntry oQueueEntry;

oQueue = new inLineLib.Queue(queueId);

oQueueEntry = oQueue.callQueueEntry(deskNo, false);

Microsoft.SqlServer.Server.SqlContext.Pipe.Send(oQueueEntry.queueNum.ToString());

}

}

And this is my CLR SQL creation code:

CREATE PROC sp_CallQueueEntry

@.queueId int,

@.deskNo int,

@.missed int

AS

EXTERNAL NAME inLineLib.[inlineCLRsql.Wrapper].CallQueueEntry

GO

sp_CallQueueEntry 4,2,0

Here is what I get as a result

System.NullReferenceException: Object reference not set to an instance of an object.

System.NullReferenceException:

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseConfigurationView.get_DefaultName()

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseMapper.MapName(String name, IConfigurationSource configSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.ConfigurationNameMappingStrategy.BuildUp(IBuilderContext context, Type t, Object existing, String id)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.DoBuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp(IReadWriteLocator locator, Type typeToBuild, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.ObjectBuilder.BuilderBase`1.BuildUp[TTypeToBuild](IReadWriteLocator locator, String idToBuild, Object existing, PolicyList[] transientPolicies)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IReadWriteLocator locator, IConfigurationSource configurationSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.EnterpriseLibraryFactory.BuildUp[T](IConfigurationSource configurationSource)

at Microsoft.Practices.EnterpriseLibrary.Common.Configuration.ObjectBuilder.NameTypeFactoryBase`1.CreateDefault()

at Microsoft.Practices.EnterpriseLibrary.Data.DatabaseFactory.CreateDatabase()

at inLineLib.Queue.getNextQueueEntry(Int32 servedBy)

at inLineLib.Queue.callQueueEntry(Int32 servedBy, Boolean callMissed)

at inlineCLRsql.Wrapper.CallQueueEntry(Int32 queueId, Int32 deskNo, Int32 missed)

What can I do to fix this?

Cheers

M

This is almost a total guess - I've never used EntLib. However, I found some one else hit this issue when EntLib was not able to find the database in the application config file: http://www.experts-exchange.com/Programming/Programming_Languages/C_Sharp/Q_21833370.html

This is likely to be the same problem you're facing. I believe you can solve this by running the Enterprise Library Config tool and specify your config file as sqlservr.exe.config in the same directory as sqlservr.exe. Or you can try copying and renaming the config file your Windows Form app is using.

Hope this works.

Steven

Message: Cannot use Large Page Extensions

Hello!
I have noticed following messaeg in SQL Server 2005 error log:'Cannot
use Large Page Extensions: lock memory privilege was not granted.' Server
is Active/Passive 64-bit SQL Server cluster with 28GB or RAM.
Can anyone explaing what this messaeg means?
Thanks,
Igor
Did you give the service account for the SQL Server service "Lock Pages in memory" user rights.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:umi2vLIRGHA.4952@.TK2MSFTNGP09.phx.gbl...
> Hello!
> I have noticed following messaeg in SQL Server 2005 error log:'Cannot use Large Page
> Extensions: lock memory privilege was not granted.' Server is Active/Passive 64-bit SQL Server
> cluster with 28GB or RAM.
> Can anyone explaing what this messaeg means?
> Thanks,
> Igor
>
|||Tibor,
Is this a good idea to do this on 64-bit vesion of SQL Server 2005? BOL
says: 'Though not required, Microsoft recommends locking pages in memory
when using 64-bit operating systems'. Will my SQL Server benefit from having
this option configured?
Thanks,
Igor
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eBUVHQIRGHA.4300@.TK2MSFTNGP14.phx.gbl...
> Did you give the service account for the SQL Server service "Lock Pages in
> memory" user rights.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:umi2vLIRGHA.4952@.TK2MSFTNGP09.phx.gbl...
>
|||Slava Oks has several articles on memory management on his blog. As I recall, he recommends locking
pages on 64 bit as well. Check it out at http://blogs.msdn.com/slavao/
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:O0LuocIRGHA.4452@.TK2MSFTNGP12.phx.gbl...
> Tibor,
> Is this a good idea to do this on 64-bit vesion of SQL Server 2005? BOL says: 'Though not
> required, Microsoft recommends locking pages in memory when using 64-bit operating systems'. Will
> my SQL Server benefit from having this option configured?
>
> Thanks,
> Igor
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in message
> news:eBUVHQIRGHA.4300@.TK2MSFTNGP14.phx.gbl...
>

Message: Cannot use Large Page Extensions

Hello!
I have noticed following messaeg in SQL Server 2005 error log:'Cannot
use Large Page Extensions: lock memory privilege was not granted.' Server
is Active/Passive 64-bit SQL Server cluster with 28GB or RAM.
Can anyone explaing what this messaeg means?
Thanks,
IgorDid you give the service account for the SQL Server service "Lock Pages in m
emory" user rights.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:umi2vLIRGHA.4952@.TK2MSFTNGP09.phx.gbl...
> Hello!
> I have noticed following messaeg in SQL Server 2005 error log:'Cannot u
se Large Page
> Extensions: lock memory privilege was not granted.' Server is Active/Pass
ive 64-bit SQL Server
> cluster with 28GB or RAM.
> Can anyone explaing what this messaeg means?
> Thanks,
> Igor
>|||Tibor,
Is this a good idea to do this on 64-bit vesion of SQL Server 2005? BOL
says: 'Though not required, Microsoft recommends locking pages in memory
when using 64-bit operating systems'. Will my SQL Server benefit from having
this option configured?
Thanks,
Igor
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:eBUVHQIRGHA.4300@.TK2MSFTNGP14.phx.gbl...
> Did you give the service account for the SQL Server service "Lock Pages in
> memory" user rights.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "imarchenko" <igormarchenko@.hotmail.com> wrote in message
> news:umi2vLIRGHA.4952@.TK2MSFTNGP09.phx.gbl...
>|||Slava Oks has several articles on memory management on his blog. As I recall
, he recommends locking
pages on 64 bit as well. Check it out at http://blogs.msdn.com/slavao/
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"imarchenko" <igormarchenko@.hotmail.com> wrote in message
news:O0LuocIRGHA.4452@.TK2MSFTNGP12.phx.gbl...
> Tibor,
> Is this a good idea to do this on 64-bit vesion of SQL Server 2005? BOL
says: 'Though not
> required, Microsoft recommends locking pages in memory when using 64-bit o
perating systems'. Will
> my SQL Server benefit from having this option configured?
>
> Thanks,
> Igor
>
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote i
n message
> news:eBUVHQIRGHA.4300@.TK2MSFTNGP14.phx.gbl...
>