Error accessing report: February 2012

Sunday, February 26, 2012

Error connecting to a SQL 2005 (June CTP) Cube using Excel 2003

When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube
,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database.
"
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
--
DuncanHi Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:

> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cu
be,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sur
e
> the external database is available, and then try the operation again. If y
ou
> see this message again, create a new data source to connect to the databas
e. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan|||If you found a solution, please let me know. I'm getting the same error
message.
Thanks a lot.
Duncan wrote:
> *When I use the PivotTable Wizard in Excel 2003 to connect to a SQL
> 2005 cube,
> the wizard successfully finds and connects to the cube, but when I
> click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator.
> Make sure
> the external database is available, and then try the operation again.
> If you
> see this message again, create a new data source to connect to the
> database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005
> (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||hpanneflek wrote:
> *If you found a solution, please let me know. I'm getting the same
> error message.
> Thanks a lot. *
I got around this by re-registering the OLAP v9.0 dll:
regsvr32 c:\program files\common files\system\oledb\msolap90.dll
This worked for me.
Good luck
Dave
Daffyd
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||Thank you! It worked.
I've been using AS 2K for 3 years now and I love it. I started playing
with AS2K5 and I am realizing that a lot of things changed. My email is
hpanneflek@.univision.net in case you have any question, I'll be glad to
help.
Thanks again.
Daffyd wrote:
> *I got around this by re-registering the OLAP v9.0 dll:
> regsvr32 c:\program files\common files\system\oledb\msolap90.dll
> This worked for me.
> Good luck
> Dave *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html

Error connecting to a SQL 2005 (June CTP) Cube using Excel 2003

Quote:

Originally posted by Duncan
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan

|||Hi both - I have exactly the same problem. Did you ever find a solution to this?
Yours in hope,

Quote:

|||Hi Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:

> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sure
> the external database is available, and then try the operation again. If you
> see this message again, create a new data source to connect to the database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan

Error connecting to .sdf database

Dear All,

I am trying to connect to a .sdf database. I am building a console application. First I got an error "Could not load file or assembly 'System.Data.SqlServerCe, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)". Then I manage to solve "Unable to load DLL 'sqlceme30.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)". So wat is the possible error on my side ?

Is it not amazing. I have been searching the forums for a solution to this specific problem for weeks now and everyone that answers has no idea what it is we are requesting. you get redirected to a thousand other sites that still can not answer this question. I dont think anyone knows how to solve this!

|||

Which version of the product are you using?

Checking the basics first: Is the product installed on your machine ( check in Add and remove programs).Also check that the System.Data.SqlServerCe.dll is in GAC (C:\windows\assembly).

If your installation was correct, then sqlceme30.dll (and other dlls) should be loaded automatically using some registry settings.

Btw, did you try reinstalling the runtime package on your machine?

Error connecting to .sdf database

Dear All,

|||

Which version of the product are you using?

Checking the basics first: Is the product installed on your machine ( check in Add and remove programs).Also check that the System.Data.SqlServerCe.dll is in GAC (C:\windows\assembly).

If your installation was correct, then sqlceme30.dll (and other dlls) should be loaded automatically using some registry settings.

Btw, did you try reinstalling the runtime package on your machine?

Error connecting through the web

Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. ThanksA just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:

>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for th
e
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:

> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>

Error connecting through the web

Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
web, and basically we're testing it out for connectivity, I set the system
dsn with the account that's in SQL server (got the server in mixed mode
auth), when I try to login to a page we put together I get this error
"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
/ConnOpen.inc, line 10"
the username mitch exists in SQL server, the tests runs fine through
ODBC>system dsn. I looked all over the forums and can't find my issue or
anything similar, if anyone's seen this before, any pointers or ideas would
be great. Thanks
A just plain "Login failed" error message indicates a bad
user name/password. If there is more with the message,
sometimes that can't help track it down. Turn on failed
login audits in SQL Server to make sure you are getting the
entire message. To turn it on, open Enterprise Manager,
right click on the server and select properties. Go to the
security tab and under Audit Level select Failed. Restart
SQL Server. The failed logins will then be logged to the SQL
Server logs.
If you are getting a full error message of login failed for
xyz. Not associated with a trusted SQL Server connection,
then it means you are trying to use a SQL login but your
server is only configured for Windows authentication. If you
need to use SQL logins, change the Authentication to SQL
Server and Windows. It's on the security tab of the
properties for SQL Server.
If you are trying to connect with Windows authentication,
then in the connection string, don't supply a user name and
password. Use Integrated Security=SSPI with an OLE DB
provider in your connection string instead of supplying a
username and password.
You may want to change drivers that you are using. The OLE
DB provider for ODBC is considered obsolete.
You can find more on connection strings at:
http://www.carlprothman.net/Default.aspx?tabid=81
-Sue
On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
<carlomd@.discussions.microsoft.com> wrote:

>Hi all, I'm new to SQL so here goes, we got a dbase we're putting up for the
>web, and basically we're testing it out for connectivity, I set the system
>dsn with the account that's in SQL server (got the server in mixed mode
>auth), when I try to login to a page we put together I get this error
>"Microsoft OLE DB Provider for ODBC Drivers error '80040e4d'
>[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'mitch'.
>/ConnOpen.inc, line 10"
>the username mitch exists in SQL server, the tests runs fine through
>ODBC>system dsn. I looked all over the forums and can't find my issue or
>anything similar, if anyone's seen this before, any pointers or ideas would
>be great. Thanks
|||Thanks for the reply, it works now, I changed the username settings in a
config file that resides in inetpub and it worked, thanks again.
"Sue Hoegemeier" wrote:

> A just plain "Login failed" error message indicates a bad
> user name/password. If there is more with the message,
> sometimes that can't help track it down. Turn on failed
> login audits in SQL Server to make sure you are getting the
> entire message. To turn it on, open Enterprise Manager,
> right click on the server and select properties. Go to the
> security tab and under Audit Level select Failed. Restart
> SQL Server. The failed logins will then be logged to the SQL
> Server logs.
> If you are getting a full error message of login failed for
> xyz. Not associated with a trusted SQL Server connection,
> then it means you are trying to use a SQL login but your
> server is only configured for Windows authentication. If you
> need to use SQL logins, change the Authentication to SQL
> Server and Windows. It's on the security tab of the
> properties for SQL Server.
> If you are trying to connect with Windows authentication,
> then in the connection string, don't supply a user name and
> password. Use Integrated Security=SSPI with an OLE DB
> provider in your connection string instead of supplying a
> username and password.
> You may want to change drivers that you are using. The OLE
> DB provider for ODBC is considered obsolete.
> You can find more on connection strings at:
> http://www.carlprothman.net/Default.aspx?tabid=81
> -Sue
> On Mon, 31 Oct 2005 14:55:06 -0800, "carlomd"
> <carlomd@.discussions.microsoft.com> wrote:
>
>

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums.aspx/sql-server/200711/1
As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
__________________________________________________ _______
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via droptable.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:

> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
Ekrem ?nsoy
"carmen413 via droptable.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums.aspx/sql-server/200711/1
>

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200711/1As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via SQLMonster.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
--
Ekrem Ã?nsoy
"carmen413 via SQLMonster.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200711/1
>

Error Connecting SQL Server 2005

Hi There,
Any one can help me suggest what to do with below problem?
while install SQL Server 2005, there is no Authentication Mode Option
prompted out for users to select The Mixed Mode. This is installed using the
correct Copyright from Ms SQL Server 2005 CD with Standard Version, where it
having CD1 and CD2. After complete setup without any error message, when
trying to open the Ms SQL Server Management Studio and connect to the server
,
there are error prompted out can not be connected. error message like below:
"an error has occurred while establishing a connection to the server. when
connecting to sql server 2005, this failure may be caused by the fact that
under the default settings sql server does not allow remote connections.
(provider: named pipes provider, error: 40 - could not open a connection to
sql server) (microsoft sql server, error: 2) "
Kindly advice
Thank you
Regards,
Carmen
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200711/1As the error says, the default installation of SQL 2005 does not
allow remote connections.
You will have to enable remote connections and [optionally] start
the SQL Server Browser service.
Detailed information:
914277 - How to configure SQL Server 2005 to allow remote
connections
http://support.microsoft.com/?kbid=914277
________________________________________
_________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
SQL troubleshooting: http://sql.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"carmen413 via droptable.com" <u21749@.uwe> wrote on 23 nov 2007
in microsoft.public.sqlserver.server:

> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode
> Option prompted out for users to select The Mixed Mode. This is
> installed using the correct Copyright from Ms SQL Server 2005 CD
> with Standard Version, where it having CD1 and CD2. After
> complete setup without any error message, when trying to open
> the Ms SQL Server Management Studio and connect to the server,
> there are error prompted out can not be connected. error message
> like below: "an error has occurred while establishing a
> connection to the server. when connecting to sql server 2005,
> this failure may be caused by the fact that under the default
> settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a
> connection to sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen|||Hello Carmen,
SQL Server 2005' s authentication mode is Windows Authentication by default
and the "sa" account will be disabled by default.
So, you can change your authentication mode by connecting your SQL Server
instance using SSMS after the setup. Go to Server Properties and Security.
You'll see the authentication modes there. I want to stress that "sa"
account is disabled by default. You can enable it (if you really need that)
from the Security\Logins nodes.
To be able to connect to your SQL Server instance, you must ensure that your
SQL Server service is running. You can check it using SQL Server
Configuration Manager or Services MMC.
This is not about remote connections at all because Remote Connections is
enabled by default for Standard and Enterprise Editions of SQL Server 2005.
It's disabled for Express and Developer Editions of SQL Server 2005 by
default.
Ekrem ?nsoy
"carmen413 via droptable.com" <u21749@.uwe> wrote in message
news:7ba5d81d07de2@.uwe...
> Hi There,
> Any one can help me suggest what to do with below problem?
> while install SQL Server 2005, there is no Authentication Mode Option
> prompted out for users to select The Mixed Mode. This is installed using
> the
> correct Copyright from Ms SQL Server 2005 CD with Standard Version, where
> it
> having CD1 and CD2. After complete setup without any error message, when
> trying to open the Ms SQL Server Management Studio and connect to the
> server,
> there are error prompted out can not be connected. error message like
> below:
> "an error has occurred while establishing a connection to the server. when
> connecting to sql server 2005, this failure may be caused by the fact that
> under the default settings sql server does not allow remote connections.
> (provider: named pipes provider, error: 40 - could not open a connection
> to
> sql server) (microsoft sql server, error: 2) "
> Kindly advice
> Thank you
> Regards,
> Carmen
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...server/200711/1
>

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.
Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting SQL instance

We are getting an error when we try to connect to one of our instances
locally. If we connect to the server remotely, we can manage it with no
problem. However, if we try to manage it from the server itself, we get the
following error:
A connection could not be established to SERVER/INSTANCE
Reason: SQL Server does not exist or access denied.
ConnectionOpen(Connect())..
Please verify SQL Server is running and check your SQL Server registration
properties (by right-clicking on the SERVER/INSTANCE node) and try again.
Our other instance works fine and the instance we are having a problem with
worked fine before, so we don't know what could be causing this. The server
is running Windows Server 2003 Standard.Are you trying to connect to the local boxes with NT or SQL security?
"DrewB" <DrewB@.discussions.microsoft.com> wrote in message
news:7634F5DF-AB13-4E3C-90D5-E45398E782EE@.microsoft.com...
> We are getting an error when we try to connect to one of our instances
> locally. If we connect to the server remotely, we can manage it with no
> problem. However, if we try to manage it from the server itself, we get
> the
> following error:
> A connection could not be established to SERVER/INSTANCE
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen(Connect())..
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the SERVER/INSTANCE node) and try again.
> Our other instance works fine and the instance we are having a problem
> with
> worked fine before, so we don't know what could be causing this. The
> server
> is running Windows Server 2003 Standard.

Error connecting new data source to SQL Server Express

In ODBC Data Source Administrator, I add the SQL Server driver, complete a name and select my local SQL Server instance, select Windows NT authentication (the client configuration is set to TCP/IP, dynamically determine port) and on clicking Next, the following errors occur:

Connection failed:
SQLState: '01000'
SQL Server error: 2
[Microsoft][ODBC SQL Server Driver][Shared Memory][ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server error: 17
[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

In a default installation of SQL Express, every user on a computer can at least connect to the server. The fact that you're connection is failing suggests that something else is wrong. Based on the error, the most likely cause is that you've mis-typed the server name. SQL Express installs to a named instance so you need to provide both the machine name and instance name in your connection, be default, the instance name is SQLEXPRESS, so your server name would be <machinename>\SQLEXPRES. For local connection you can replace <machinename> with "(local)" or "." Note that it's a back slash, people commonly use the forward slash which will cause an error.

If that doesn't help, verify which SQL driver you are using, there are two of them. It looks like you're using the Native Client, which is good, but if you're using the old MDAC driver (just says "SQL Server" in the list) then you'll need to enable the TCP protocol for the Server using the SQL Configuration Manager. MDAC ODBC connection go through TCP, even for local connections.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami

Error connecting new data source to SQL Server Express

I note that in the Help it says: "The SQL Server system administrator must have associated your Microsoft Windows login with a SQL Server login ID".

Is this the problem? If so, where do I make this association?

Thanking you in anticipation.

Mike

|||

Hi,

I would suggest to refer http://support.microsoft.com/kb/322336 & http://support.microsoft.com/kb/328306/en-us

Hemantgiri S. Goswami

Error connecting in Management Studio

Hello,

I am having problems connecting to my SQL Server instance with Management Studio; basically the setup is as follows;

*Single server running windows 2003 enterprise - in a workgroup not domain
*SQL Server is installed on this machine
*When I try and connect from the same machine using its own IP address and Windows authentication I get the 18452 error "login failed for {NULL} user"

I am testing it like this because Sharepoint is failing in configuration wizard because it is connecting the same way - at least the login failure audit logs say the same.

Many thanks for answers

With which application are you trying to connect ? Did you try another application yet ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

This commonly happens with trusted authentication when your local user does not translate to the other machine (e.g. LOCAL_SYSTEM or NETWORK_SERVICE, etc.). Naturally, if you translate to the IP address, even on loopback, the account must be one that can be understood remotely, so in this case your client and server are the same machine, but the same truth applies. Your user must be recognizable from a remote connection to this machine. Try rasing into the machine from a remote machine under the user account to see if it works. If it doesn't ras, your user needs to be reconfigured/reselected.

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/ias2000a.mspx

http://ablog.apress.com/?p=1127

http://support.microsoft.com/kb/215383

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/kerberos.mspx

It could also be possible that your machine is not running the correct authentication protocols to support Trusted authentication on your OS. I don't actually know how to configure users/authentication on Windows workgroups/domains so how this is addressed is beyond me.

Hope that helps,

John

|||Thanks for the response John.

The user I am using is the default "Administrator" (I know bad practice) for testing.

It is definatly something to do with the user not being understood in the loopback.

However like you, I have no idea how to fix this :/

Cheers
|||Try a different user or modifying your administrative user to have remote access. Administrator is one of those users that is traditionally a local account only. Optionally, you could try fiddling with the user manager and enabling remote access for the administrator account, but I am fairly certain that would open you up to some evil attacks.|||Can you tell us how you connect exactly?
Are you using OPENROWSET?

Error connecting in Management Studio

Hello,

I am having problems connecting to my SQL Server instance with Management Studio; basically the setup is as follows;

I am testing it like this because Sharepoint is failing in configuration wizard because it is connecting the same way - at least the login failure audit logs say the same.

Many thanks for answers

With which application are you trying to connect ? Did you try another application yet ?

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/ias2000a.mspx

http://ablog.apress.com/?p=1127

http://support.microsoft.com/kb/215383

http://www.microsoft.com/technet/prodtechnol/windows2000serv/deploy/confeat/kerberos.mspx

Hope that helps,

John

|||Thanks for the response John.

The user I am using is the default "Administrator" (I know bad practice) for testing.

It is definatly something to do with the user not being understood in the loopback.

However like you, I have no idea how to fix this :/

Error connecting from classic ASP

I'm haveing some problems with using SQL Server in a classic ASP app.

When trying to connect with the db I get the error:

Microsoft SQL Native Client error '80004005'

TCP Provider: No connection could be made because the target machine actively refused it.

The Windows 2003 server runs both the SQL server 2005 express and IIS.

Connectionstring: "Provider=SQLNCLI;Server=KSP;Database=KSB;UID=sa;PWD=;"

I don't have a good answer for this one; it seems a bit like a permissions issue, you might want to check what user context your ASP app is running in and make sure that user has permission to the database file or server.

You should also consider asking this question in the .NET Data Access forum or in the ASP.NET fourms. The folks that hang out there have probably had more experience with ASP than I have.

Regards,

Mike Wachal
SQL Express team

-
Check out my tips for getting your answer faster and how to ask a good question: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=307712&SiteID=1

|||

Sql server express is a named instance, so you need to specify <servername>\sqlexpress in you connection string.

Check this out.

http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

|||

Thank both of you for your advice. It was the <servername>\sqlexpress which was the problem.

Error connecting Excel to Analysis Service for browsing cube

I have created a cube. Now when I open excel so that to browse the cube in the excel pivot table i am getting connection refused error? I am using olap 9.0 to connect to my cube which is deployed on the sqlserver 2005 analysis server. server is up and running.ok i found the solution. we need to reregister the olap 9.0 provider before we can use it to connect SQL Server 2005 Analysis Service Cube with Excel Pivot Table :
regsvr32 "c:\program files\common files\system\ole db\msolap90.dll"|||

Hi,

I having the similar problem with you. But no sure whether your error message is same with me. Here i get the error message as below:

Connection Failed

SQL State: '28000'

SQL Server Error: 18456

[Microsoft][ODBC SQL Server][SQL Server] Login failed for user 'domain\userida'

I am using olap services 8.0 & sqlserver 2000.

I checked this userida is properly created in the cube under a cube role said 'Accounts'. This role contain of abt 6 user id. Others user id is work fine except for this userida.

Any ideas to solve this issue.

Thanks in advance.

Error connecting Database Server

Hi,

I am getting the following error when i am trying to connect to the database server installed on different box.

"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)"

When i searched google, some postings suggested to enable the TCP/IP and Named Pipes Protocols from SQL Server configuration Manager. I did so and also ran mofcomp command. But even after doing this i am not able to connect to the server. Following is my connection string.

Could any one please tell me what else the configuration settings i need to do in order to connect to the database from my application.

There are a couple of things to look at

1/. ensure your SQL Server 2005 instance allows remote connections

2/. make sure your firewall is not blocking any incoming connections

Error connecting

Cannot open database requested in login <DatabaseName>. Login fails.
Login failed for user <DOMAINNAME\User>.
Please help."Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> Cannot open database requested in login <DatabaseName>. Login fails.
> Login failed for user <DOMAINNAME\User>.
>
How are you attempting to connect? Can you reproduce this using Query
Analyzer? What login and database permissions have you defined for this
user?
Steve|||Hello, Steve,
How can I manage SQL Server's users, for example, how to change the 'sa' pas
sword?
Is it can only be done by using 'Enterprise Manager'?
LLF
--
There's an unfinished grid inside my head...
"Steve Thompson" wrote:

> "Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
> news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> How are you attempting to connect? Can you reproduce this using Query
> Analyzer? What login and database permissions have you defined for this
> user?
> Steve
>
>|||LLF,
You can use Enterprise Manager if you wish. Enterprise
Manager is really just executing T-SQL commands for you so
you can manage these through Query Analyzer or any other
tool that can connect to and execute queries on SQL Server.
Passwords are changed using sp_password.
You can add logins using sp_grantlogin for Windows logins or
sp_addlogin for SQL logins.
You can add users to a database using sp_grantdbaccess.
You can find all of these system stored procedures
documented in SQL Server Books Online.
-Sue
On Tue, 27 Jul 2004 10:01:37 -0700, LLF
<LLF@.discussions.microsoft.com> wrote:

>Hello, Steve,
>How can I manage SQL Server's users, for example, how to change the 'sa' pa
ssword?
>Is it can only be done by using 'Enterprise Manager'?
>LLF|||Thanks a lot !
LLF
There's an unfinished grid inside my head...
"Sue Hoegemeier" wrote:

> LLF,
> You can use Enterprise Manager if you wish. Enterprise
> Manager is really just executing T-SQL commands for you so
> you can manage these through Query Analyzer or any other
> tool that can connect to and execute queries on SQL Server.
> Passwords are changed using sp_password.
> You can add logins using sp_grantlogin for Windows logins or
> sp_addlogin for SQL logins.
> You can add users to a database using sp_grantdbaccess.
> You can find all of these system stored procedures
> documented in SQL Server Books Online.
> -Sue
> On Tue, 27 Jul 2004 10:01:37 -0700, LLF
> <LLF@.discussions.microsoft.com> wrote:
>
>

Error connecting

Cannot open database requested in login <DatabaseName>. Login fails.
Login failed for user <DOMAINNAME\User>.
Please help.
"Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> Cannot open database requested in login <DatabaseName>. Login fails.
> Login failed for user <DOMAINNAME\User>.
>
How are you attempting to connect? Can you reproduce this using Query
Analyzer? What login and database permissions have you defined for this
user?
Steve
|||Hello, Steve,
How can I manage SQL Server's users, for example, how to change the 'sa' password?
Is it can only be done by using 'Enterprise Manager'?
LLF
There's an unfinished grid inside my head...
"Steve Thompson" wrote:

> "Viktor Zadro" <viktor.zadro@.tel.net.ba> wrote in message
> news:ukzXI7IcEHA.3016@.tk2msftngp13.phx.gbl...
> How are you attempting to connect? Can you reproduce this using Query
> Analyzer? What login and database permissions have you defined for this
> user?
> Steve
>
>
|||LLF,
You can use Enterprise Manager if you wish. Enterprise
Manager is really just executing T-SQL commands for you so
you can manage these through Query Analyzer or any other
tool that can connect to and execute queries on SQL Server.
Passwords are changed using sp_password.
You can add logins using sp_grantlogin for Windows logins or
sp_addlogin for SQL logins.
You can add users to a database using sp_grantdbaccess.
You can find all of these system stored procedures
documented in SQL Server Books Online.
-Sue
On Tue, 27 Jul 2004 10:01:37 -0700, LLF
<LLF@.discussions.microsoft.com> wrote:

>Hello, Steve,
>How can I manage SQL Server's users, for example, how to change the 'sa' password?
>Is it can only be done by using 'Enterprise Manager'?
>LLF
|||Thanks a lot !
LLF
There's an unfinished grid inside my head...
"Sue Hoegemeier" wrote:

> LLF,
> You can use Enterprise Manager if you wish. Enterprise
> Manager is really just executing T-SQL commands for you so
> you can manage these through Query Analyzer or any other
> tool that can connect to and execute queries on SQL Server.
> Passwords are changed using sp_password.
> You can add logins using sp_grantlogin for Windows logins or
> sp_addlogin for SQL logins.
> You can add users to a database using sp_grantdbaccess.
> You can find all of these system stored procedures
> documented in SQL Server Books Online.
> -Sue
> On Tue, 27 Jul 2004 10:01:37 -0700, LLF
> <LLF@.discussions.microsoft.com> wrote:
>
>

Error connectin to SQL 2005 Express

I've just installed Visual Studio 2005 and SQL Server 2005 Express beta 2
(all on my local PC). I try to connect to the SQL server from studio using
"Tools/Connect to database" selecting my local pc in the "Select or enter a
server name" combo box. I can select my pc's name but when I try to expand
the "Select or enter database name" combo or press the "Test connection"
button I get the following error:
"Shared memory provider: The specified module could not be found"
Any ideas?
Peter
http://www.aspfaq.com/sql2005/show.asp?id=3
Also, please use the SQL Server 2005 forums.
http://www.aspfaq.com/sql2005/show.asp?id=1
http://www.aspfaq.com/
(Reverse address to reply.)
"Peter Hemmingsen" <phe@.softco.dk> wrote in message
news:#YcDp4UpEHA.4004@.TK2MSFTNGP10.phx.gbl...
> I've just installed Visual Studio 2005 and SQL Server 2005 Express beta 2
> (all on my local PC). I try to connect to the SQL server from studio using
> "Tools/Connect to database" selecting my local pc in the "Select or enter
a
> server name" combo box. I can select my pc's name but when I try to expand
> the "Select or enter database name" combo or press the "Test connection"
> button I get the following error:
> "Shared memory provider: The specified module could not be found"
> Any ideas?
> Peter
>

error configure

Hi every1,

I have problem about configuration in Merge Replication.

First, I configure for SQL Server 2000, expand Replication> Publication>New Publication>Choose Publication Database, I choose pubs>Select Publication Type, choose Merge Replication>Specify Subscribers Type, choose Servers running SQL Server 2000 and Devices running SQL Server CE>Specify article (ex. authors)…>Finish. I configure succeeded (A snapshot of 1 article(s) is generated).

Snapshot folder reference to path: \\server_name\C$\Program Files\Microsoft SQL Server 2005 Mobile Edition\Server\Replication

Next, I configure for SQL Server Mobile Agent, Subscriber Type, choose SQL Server Mobile Edition>Web server, choose Create a new virtual directory>Alias: Replication (reference to the path: C:\Program Files\Microsoft SQL Server 2005 Mobile Edition\Server\Replication)..>Client Authentication, choose Client will connect anonymously….>Snapshot share access, enter \\server_name\Replication =>error: The share '\\server_name\Replication'cannot be accessed. Please specify a new share. Why that?

I want to ask u I configure that correctly? If Subscriber is Pocket PC Emulator, what is subscriber ’sproperty of SqlCeReplication (Windows PocketPC Emulator?)?

Plz help me. Thanks so much.

I need your help very much. Please.|||

Firstly you should not use \\server_name\c$\.... By C$ you are assuming that the login that syncs has access to this machine's c$.

You should use a share: \\servername\repl.

Then give this share name created in the Configure virtual directory.

And I do not understand your last question about emulator.

error configure

Hi every1,

I have problem about configuration in Merge Replication.

Snapshot folder reference to path: \\server_name\C$\Program Files\Microsoft SQL Server 2005 Mobile Edition\Server\Replication

I want to ask u I configure that correctly? If Subscriber is Pocket PC Emulator, what is subscriber ’sproperty of SqlCeReplication (Windows PocketPC Emulator?)?

Plz help me. Thanks so much.

I need your help very much. Please.|||

Firstly you should not use \\server_name\c$\.... By C$ you are assuming that the login that syncs has access to this machine's c$.

You should use a share: \\servername\repl.

Then give this share name created in the Configure virtual directory.

And I do not understand your last question about emulator.

error configuration

I want to use custom error configuration for a single dimension.

When I set the error configuration properties for a single dimension in Visual Studio, process this dimension and process the cube then the custom error configuration settings are ignored.

When I set custom error configuration settings for the cube in Visual Studio these settins are also ignored.

When I set the custom error configuration settings in the Process Cube Window (Change Settings - Dimension Key errors) then these settings are applied to all dimensions.

How can I use custom error configuration for a single dimension and why are my settings in Visual Studio ignored.

Thanks for any reply.

They should not be ignored. Probably you work in the project mode and do not deploy before opening the processing dialog.

When you set it in VS you modify the error configuration only for the local data. If you are in project mode then you need to deploy your changes onto the server so that the changes would be known. Usually the deployment also means processing. If you just click that button to open the processing dialog in VS then it establishes a server connection and processes whatever has been previously deployed, which contains the old error configuration.

If you are in on-line mode then you need to save the object (dimension, cube) once you have changed the error configuration. Saving will propagate the meta data changes onto the server and once you open the processing dialog it will process with the new error configuration.

Saving in project mode will persist your changes on disk and not on the server. This is why in project mode you need deployment.|||

Thanks for your reply.

I have deployed my changes. I have the same behaviour when I am using SQL Server Management Studio on the server. Here I can view the current error configuration of the dimension:

Use default error configuration: disabled

Key error action: Convert To Unknown

Ignore errors

Key not found: Report And Continue

Duplicate key: Ignore Error

Null key converted to unknown: Ignore Error

Null key not allowed: IgnoreError

Error log path: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log\analyzer.log

When I rightclick on the cube and select Process to open the Process cube window and start processing with the default settings I still get a key not found error (for this dimension with an individual configuration error setting) and processing stops.

When I change the error configuration settings in SQL Server Management Studio for the cube this settings are ignored when I process via the Process Cube window with the default settings.

And when I change the error configuration settings for the process (in the Process Cube window) these settings are taken for all dimensions and the individual settings of the dimensions are ignored.

Do I have to start the process in another way?

Are there any preconditions like schema optimization in AS 2000?

|||

> I still get a key not found error (for this dimension with an individual configuration error setting) and processing stops.

Does the processing dialog box show that the processing failed? Stops could mean it succeeded with errors. Depends how much time it takes to process your cube.

Unless you have a repro, which you could send i will need to model the situation according to your description and get back to you with the results.

|||

try to configure like this..

Click the Cube properties...

Goto Error configuration....and set it to custom...

and then expand it and set the 'Key Error Limit' as -1 save it and process the cubbe.

Hope this helps you.

|||I have made some repro simulation and asked people a question and here what has been found. When you specify Ignore Error ( -1 for KeyErrorLimit ) on a dimension it does not apply to the problems with fact data. It applies to the case when your dimension consists of attributes having sources to different tables - snowflake dimensions. The content in these tables might have referential integrity problems. Specifying -1 KeyErrorLimit will allow processing the dimension.

When you specify -1 KeyErrorLimit for a cube it allows processing when the fact tables do not have corresponding primary key in any of the dimension tables.

It is not possible to declare ignoring referential integrity problems between fact table and only one dimension table. Once it is defined on a cube or partition then referential integrity problems with all the dimensions are ignored.

In my test case i created a simple database, which has 2 dimension tables and one fact table. The fact table contained records with some foreign key values absent in the dimension tables. I created 2 dimensions and one measure group. In order to process successfully i just had to specify -1 KeyErrorLimit in ErrorConfiguration of the cube. Everything processed fine.

Maybe you have 2 types of referential integrity problems at the same time and in order to resolve them you need to specify -1 KeyErrorLimit on the dimension and on the cube.|||

Hi Andrew,

thank you very much for your detailed explanation (and also thanks to rockworld for your hint).

So it was my misunderstanding how to use the custom error configuration on a dimension.

error conection frm clients to the sqlserver

hi
dear members
we have a program that its database is SQLserver2000 that installed on a
computer with ' MIS' name.the type of SQLserver installation is mixed mod
e
(not Authentication ). so , 2 weeks ago the program did run on all of the
network clients without login to the SQlserver besuse the sqlserver is mixed
mod. but now our SQl server has a problem besouse for runing the program on
any client on the network, first we have to login to the SQLserver compute
r
then run the application program . but we want to run the software with
sqlserver database without login to SQLserver computer.
note: My connection from program to SQLserver is ADO Connection with mixed
mode(user name=SA , password = blank""first we have to login to the SQLserver computer
then run the application program ""
Not sure what you mean...are you saying that when you open the application,
you get a username/password prompt, or are you actually logging into the
SQL Server via remote desktop/terminal server?
What is the application? Access? VB.Net?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"ahi" <ahi@.discussions.microsoft.com> wrote in message
news:594B3C9D-D780-462E-93B7-C3CF683AA3D3@.microsoft.com...
> hi
> dear members
> we have a program that its database is SQLserver2000 that installed on a
> computer with ' MIS' name.the type of SQLserver installation is mixed
> mode
> (not Authentication ). so , 2 weeks ago the program did run on all of the
> network clients without login to the SQlserver besuse the sqlserver is
> mixed
> mod. but now our SQl server has a problem besouse for runing the program
> on
> any client on the network, first we have to login to the SQLserver
> computer
> then run the application program . but we want to run the software with
> sqlserver database without login to SQLserver computer.
> note: My connection from program to SQLserver is ADO Connection with mixed
> mode(user name=SA , password = blank

error conection frm clients to the sqlserver

hi
dear members
we have a program that its database is SQLserver2000 that installed on a
computer with ' MIS' name.the type of SQLserver installation is mixed mode
(not Authentication ). so , 2 weeks ago the program did run on all of the
network clients without login to the SQlserver besuse the sqlserver is mixed
mod. but now our SQl server has a problem besouse for runing the program on
any client on the network, first we have to login to the SQLserver computer
then run the application program . but we want to run the software with
sqlserver database without login to SQLserver computer.
note: My connection from program to SQLserver is ADO Connection with mixed
mode(user name=SA , password = blank
""first we have to login to the SQLserver computer
then run the application program ""
Not sure what you mean...are you saying that when you open the application,
you get a username/password prompt, or are you actually logging into the
SQL Server via remote desktop/terminal server?
What is the application? Access? VB.Net?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
www.experts-exchange.com - experts compete for points to answer your
questions
"ahi" <ahi@.discussions.microsoft.com> wrote in message
news:594B3C9D-D780-462E-93B7-C3CF683AA3D3@.microsoft.com...
> hi
> dear members
> we have a program that its database is SQLserver2000 that installed on a
> computer with ' MIS' name.the type of SQLserver installation is mixed
> mode
> (not Authentication ). so , 2 weeks ago the program did run on all of the
> network clients without login to the SQlserver besuse the sqlserver is
> mixed
> mod. but now our SQl server has a problem besouse for runing the program
> on
> any client on the network, first we have to login to the SQLserver
> computer
> then run the application program . but we want to run the software with
> sqlserver database without login to SQLserver computer.
> note: My connection from program to SQLserver is ADO Connection with mixed
> mode(user name=SA , password = blank

Error Condition for Updates

Hi,

I have a series of Updates that I perform on 7 tables. I would like to execute these updates on a nighly basis via a job. I have the update statements lined up in a stored proc.

So I have -

Create Proc Update
AS
SET NOCOUNT ON

DECLARE @.RETURNVALUE int
DECLARE @.ERRORMESSAGETXT varchar(510)
DECLARE @.ERRORNUM int

set @.RETURNVALUE = 0

BEGIN --Start here

Update table1
Update table2
.
.
.
Update table7

SELECT @.ERRORNUM = @.@.ERROR
IF @.ERRORNUM = 0
SELECT @.RETURNVALUE = 0
ELSE
BEGIN
SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages]
WHERE error = @.@.ERROR
RAISERROR (@.ERRORMESSAGETXT, 16, 1)
SELECT @.RETURNVALUE = 1
END
RETURN @.RETURNVALUE
END -- END HERE

--

Is the error checking at the appropriate place? Should I have error conditions after every update? If yes then what condition do I check for?

Thanks@.@.ERROR only shows the result of the most recent statement. It is cleared for the next statement. Therefor your code is only going to indicate whether an error occured on Update Table7.

You will need to check for an error after each critical step, and then store the results of the error check. You can store it in a single value like:
@.ERROR_MONITOR = @.ERROR_MONITOR + @.@.ERROR
...which will result in a value greater than zero if any errors occured. Or you can store the results of each check separately (@.UPDATETABLE1ERROR, @.UPDATETABLE2ERROR..etc).|||So is this correct. Check the where clause in the ELSE part and the statement after Update Table 7.
----
Update table1
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR
Update table2
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR
.
.
.
Update table7
SELECT @.ERRORNUM = @.ERRORNUM + @.@.ERROR

IF @.ERRORNUM = 0
SELECT @.RETURNVALUE = 0
ELSE
BEGIN
SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages]
WHERE error = @.@.ERROR (OR is this @.ERRORNUM)
RAISERROR (@.ERRORMESSAGETXT, 16, 1)
SELECT @.RETURNVALUE = 1
END
RETURN @.RETURNVALUE

Let me know.

Thanks|||@.ERRORNUM holds the sum of all the error message IDs, so it can be used to determine whether any error occured but if more than one error occured then it is useless for looking up the error description.

"SELECT @.ERRORMESSAGETXT = description FROM [master].[dbo].[sysmessages] WHERE error = @.@.ERROR "
...will, again, only give you the error message for the last error to occur.

If you want to be able to handle multiple errors, create a varchar variable and append any error text to it after each critical step.

Depending on your process, you may just want to exit the procedure after the first error...|||Don't call your procedure "Update". And I don't think you could actually compile what you posted.

And if you are really interested in capturing all the errors while continuing to do your updates, then you'll need a @.temptable to acquire a value of @.@.error on each update. At the end you would parse a string of all errors by joining this table with sysmessages and scrolling through it while concatenating [description] into a varchar variable.

Error concatenating string

I am trying to create a job that, as one of its steps, will kick off a
DTS package. As part of the command parameter, I need to concat a
system variable (@.@.SERVERNAME) to a constant string. I am receiving an
error about incorrect syntax near the +.

Here is the code for the job step.

-- Add the job steps
EXECUTE @.ReturnCode = msdb.dbo.sp_add_jobstep@.job_id = @.JobID,
@.step_id = 1,
@.step_name = N'Import OCC Series Data',
@.command = N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME,
@.database_name = N'',
@.server = N'',
@.database_user_name = N'',
@.subsystem = N'CmdExec',
@.cmdexec_success_code = 0,
@.flags = 2,
@.retry_attempts = 0,
@.retry_interval = 1,
@.output_file_name = N'',
@.on_success_step_id = 0,
@.on_success_action = 3,
@.on_fail_step_id = 0,
@.on_fail_action = 3
IF (@.@.ERROR <> 0 OR @.ReturnCode <> 0) GOTO QuitWithRollback

If I just try SELECT N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME, everything works fine. I even tried declaring a local
variable named @.command and setting it in the select statement, but no
dice."Jason" <JayCallas@.hotmail.com> wrote in message
news:f01a7c89.0402051028.4aa7015e@.posting.google.c om...
> I am trying to create a job that, as one of its steps, will kick off a
> DTS package. As part of the command parameter, I need to concat a
> system variable (@.@.SERVERNAME) to a constant string. I am receiving an
> error about incorrect syntax near the +.
> Here is the code for the job step.
> -- Add the job steps
> EXECUTE @.ReturnCode = msdb.dbo.sp_add_jobstep @.job_id = @.JobID,
> @.step_id = 1,
> @.step_name = N'Import OCC Series Data',
> @.command = N'DTSRun /F
> D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
> @.@.SERVERNAME,
> @.database_name = N'',
> @.server = N'',
> @.database_user_name = N'',
> @.subsystem = N'CmdExec',
> @.cmdexec_success_code = 0,
> @.flags = 2,
> @.retry_attempts = 0,
> @.retry_interval = 1,
> @.output_file_name = N'',
> @.on_success_step_id = 0,
> @.on_success_action = 3,
> @.on_fail_step_id = 0,
> @.on_fail_action = 3
> IF (@.@.ERROR <> 0 OR @.ReturnCode <> 0) GOTO QuitWithRollback
> If I just try SELECT N'DTSRun /F
> D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
> @.@.SERVERNAME, everything works fine. I even tried declaring a local
> variable named @.command and setting it in the select statement, but no
> dice.

You can't build a parameter value 'dynamically' like that, but assigning the
entire string to a variable first should work:

declare @.mycommand nvarchar(1000)
set @.mycommand = N'DTSRun /F
D:\Databases\Scripts\DTS\ImportOCCSeriesData.dts /A DbName:8=' +
@.@.SERVERNAME

EXECUTE msdb.dbo.sp_add_jobstep
...
@.command = @.mycommand
...

What error did you get when you tried this?

Simon|||I ended up figuring that out and doing exactly what you suggested.
Something I did not know about passing parameters to stored
procedures...

The error I had gotten was
Incorrect syntax at '+'

Thanks for the help.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

error comming at insert stmt

assume connection is established and photo cloumn as data type as image in sql table.

str_insert ="INSERT INTO SIS_TeachingStaff VALUES('TSMT2','V.RAJANIKANTH','LECTURER','TEACHING STAFF','Msc(Maths)','" & Emp_pic.Image &"' "

cmd =New SqlCommand(str_insert, conn)

cmd.Connection = conn

cmd.ExecuteNonQuery()

Error at insert stmt: Operator '&' is not defined for types 'string' and 'system.drawing.image'

")" is missed at the end .Try this:

str_insert ="INSERT INTO SIS_TeachingStaff VALUES('TSMT2','V.RAJANIKANTH','LECTURER','TEACHING STAFF','Msc(Maths)','" & Emp_pic.Image &"') "

error column

Hi,

There is an error output from one oledb destination which causes error to another which populated a table called tblFailedRows.

I have mapped the errorcolumn to the errorcolumn in tblFailedRows.

When looking at the errorcolumn in tblFailedRows I see just numbers not the column name.

How do I get the column name that causes the error?

Thanks

Here's a thread with information on this:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1509836&SiteID=1

error column

Hi,

Using SSIS, while importing (source i.e. .csv into destination i.e. sql server table), how is it possible to log the source COLUMN which causes the error in the row?

Thanks

Hello Arkiboys,

Many data flow components, including most sources and destinations, support an "Error Ouput" concept whereby you can work with the individual rows of data that could not be successfully processed by a component. This error output includes an ErrorCode and ErrorColumn that you can use in many cases to determine the column that is causing the error.

For more information, I'd suggest taking a look at this:

http://msdn2.microsoft.com/en-us/library/ms141679.aspx

-David

|||

Hi,

I followed the lonk.
Not sure why I do not get the error columns expanded as it says in the link.

Still do not know how to pull the column out i.e. I have a stored procedure which I would like to record the error columns. How do I get these error columns name and rows?

Thanks

Error Codes?

My data flow component is throwing an error and the only help I get is the following:

error code: -1071607694

error column: 257

What in the world does this mean? Can it get more cryptic than this?

Search is your friend.

http://wiki.sqlis.com/default.aspx/SQLISWiki/0xC0209072.html

You have a conversion issue.

Error code: 0x80004005

I created a package that refreshes tables on one SQL Server to another SQL Server. First, I use an ExecuteSQL task to truncate the tables. Then I use a Data Flow task to copy the tables from one server to the other. Finally I update a log table. It was working fine with four tables. I added another table to the refresh and now I get these error messages:

[Source - RbcAcctSegment [1096]] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Unspecified error". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

I made a few changes in the Data Flow task. In the Properties of the Destination components I changed the OpenRowset property to include the database name beside the table name. Not all the Destination components had the database name.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

|||Now that you mention, I do remember we did have a similar error when we had around 20 in a data flow and then we moved some of them out to a new data flow and it worked fine. I had to put a precedence between the two.

Error code: 0x80004005

[Source - RbcAcctSegment [1096]] Error: Opening a rowset for "[dbo].[RbcAcctSegment]" failed. Check that the object exists in the database.

[DTS.Pipeline] Error: component "Source - RbcAcctSegment" (1096) failed the pre-execute phase and returned error code 0xC02020E8.

RbcAcctSegment is the new table that I added. The errors occur in the Data Flow task. We have tried running this on a different workstation with the same results.

What would cause this?

Fred

Try changing the connection propery 'Retain Same Connection' to FALSE.|||The 'Retain Same Connection' property is already set to FALSE for both Source and Destination Connection Managers.|||

I believe I found the problem.

Before it was [dbo].[TableName] and I changed it to [DatabaseName].[dbo].[TableName].

Fred

|||

It wasn't the problem. It worked one time.

Is there a limit on how many tables you can copy in one DataFlow task?

Fred

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this case
http://groups.google.co.uk/group/mic...hread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role +'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this casehttp://groups.google.co.uk/group/mi...thread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role+'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

error code sql server

Good morning
MOM server 2005 prompt this message during the installation
Failed to setup database security.
Error code: -2147217900 (user, group, or role 'SC DW DTS'
already exist in the current database)
what can i do in this casehttp://groups.google.co.uk/group/microsoft.public.mom/browse_thread/thread/9
fc353baf7bde8b8/45c77c865aeb54a8?lnk=st&q=user%2C+group%2C+or+role+'SC+DW+DT
S'+already+exists&rnum=1&hl=en#45c77c865aeb54a8
"Djeff" <e.djeff@.free.fr> wrote in message
news:mn.b33c7d5c80e5082d.46131@.free.fr...
> Good morning
> MOM server 2005 prompt this message during the installation
> Failed to setup database security.
> Error code: -2147217900 (user, group, or role 'SC DW DTS'
> already exist in the current database)
> what can i do in this case
>

Error Code of 3238395904 and 3240034316

I get the following error for a cube that used to process just fine.

Executed as user: PREMIER_AD\SQLExec. ...ts xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults"><root xmlns="urn:schemas-microsoft-com:xml-analysis:empty"><Exception xmlns="urn:schemas-microsoft-com:xml-analysis:exception" /><Messages xmlns="urn:schemas-microsoft-com:xml-analysis:exception"><Error ErrorCode="3238395904" Description="OLE DB error: OLE DB or ODBC error: Unspecified error." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034316" Description="Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'Vw PASBSCD1291 Fact', Name of 'Drillthrough Data' was being processed." Source="Microsoft SQL Server 2005 Analysis Services" HelpFile="" /><Error ErrorCode="3240034317" Description="Errors in the OLAP storage engine: An error occurred while the 'Reason' attribute of the 'Drillthrough Data' dimension from the 'Pas' database was being processed." Source="Microsoft SQL Server 200... The step succeeded.

I have no idea what Error Codes 3238395904 and 3240034316 are.

Looks like error belongs to the OLEDB provider you are using.

The error message reported by OLEDB provider is just "Unspecified error"

Looks like something went wrong with your relational database connection. Test your conneciton. See if you can process any other objects based on the same data source.

Hope that helps.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks, Edward.

The problem seems to have resolved itself. I believe the connectivity issues might be related to capacity problems were were having with our relational database late last week.

Dan

Error Code of 3238395904 and 3240034316

I get the following error for a cube that used to process just fine.

I have no idea what Error Codes 3238395904 and 3240034316 are.

Looks like error belongs to the OLEDB provider you are using.

The error message reported by OLEDB provider is just "Unspecified error"

Looks like something went wrong with your relational database connection. Test your conneciton. See if you can process any other objects based on the same data source.

Hope that helps.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Thanks, Edward.

The problem seems to have resolved itself. I believe the connectivity issues might be related to capacity problems were were having with our relational database late last week.

Dan

Error Code if Row is locked

Hallo,
if a row is locked in SQLExpress and an other user want to update this row,
SQLExpress waits until timeout. And than I get the errormessage "timeout".

What I need is an immediately errormessage "row is locked" !

So that the user dont need to wait if the row is locked
and I need the correct errormessage so that I can check
if there is a databaseproblem or only the row locked
because an other user is editing the same rows.

Thx Wolfgang
(please excuse my english)

hi,

SQL Server does not provide this feature as this should be managed on the client side of the application and not server side on SQL Server...

you can thus set an appropriate timeout on the ado/ado.net command you are using, and then take the required decision once the command result in an exception..

but you have to fine tune your timeout, depending on SQL Server load, bandwidth, network trafic, ..

regards

|||

Thank you for your help!

I need a small timeout if the Updatecommand "meets" locked rows.
I do not want to reduce the timeout for the SqlCommand itself.

The solution i have found is to use the keyword NOWAIT in the SQL-Statement.

UPDATE table WITH (NOWAIT) SET ......

I think this works okay, but I have not found something to set timeout for locks to 1 sec
and timeout for SQLCommand to 15 sec.

Thany you for your help.
Wolfgang

error code from DTEXEC not 0 nor 1

I would like to send back to MS-DOS (ERRORLEVEL) an error code 2 ( different from 0 and 1) via a scripting Task.

Our package are started with the DTEXEC Utility.

In general, how can i send back a flag saying "There were warnings" during the execution of a Package

Warnings can happen with successful package executions, and for that matter, so can errors.

There are a numerous ways to figure out there were warnings though, such that a shell caller is aware of that fact.

One, capture the console output from dtexec and look through the captured text for the warning event.

Two, create a console utility which calls Package.Execute() and iterates through the .Warnings collection. If the count > 0, return what you want as the process exit code.

Three, use logging. Configure the package to use the native SSIS logging facilities to write log entires. Read the produced log provider for warning events.

Four, use a package level OnWarning event handler. Inside the event handler, set something external to the package (file, db, message queue, doesn't matter) which is readable post-execution.

Sunday, February 26, 2012

Blog Archive

About Me