Connection to Red Brick

Hi all,

Is it possible to connect to an IBM Redbrick Database via Data Sources in AS 2005? I can't get to ODBC's and don't see an OLE driver.

Thanks in advance,

Mark

You must have a driver AND a cartridge that will work with Redbrick. The driver is pretty straightforward. The cartridge is an XSLT file that translates an internally generated XML-based query into a valid SQL statement for submission to the source system. On my system, the cartidges are available at:

C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\Cartridges

If a cartridge is not available for your specific system (which is the case for Redbrick), SSAS attempts to use the sql2000.xsl cartridge. This might work for you, but I'm not certain.

Another optoin for you is to create a set of views in SQL Server that use the OPENROWSET function to establish the connection to Redbrick for you. You might be able to then expose those views to SSAS and since SSAS has cartridges for SQL Server this might work out.

Good luck,

Bryan

|||

Thanks for the suggestions/guidance Bryan.

I appreciate the help.

connection strings, trusted-connection VS username-password, SQL Server 2005 Express

All --

Please help.

I have some questions about connection strings.

BACKGROUND...

Note that I am using the "SQL Native Client OLE DB Provider", SQL Sever 2005 Express, ASP.NET, C#.NET, and VS.NET 2005.Note that I do not want to use the "Attach a database file" type of connection string.Note that I am using the sitehttp://www.ConnectionStrings.com as a reference.Note that this "Standard security" connection string...
<add name="LocalSqlServer" connectionString="Server=MYTEST\OFFICESERVERS;Database=MyDatabase;Uid=MyDatabaseUser;Pwd=MyDatabasePassword;" />
...does not work and causes the following run-time error...
A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)Note that this "Trusted connection" connection string...
<add name="LocalSqlServer" connectionString="Server=MYTEST\OFFICESERVERS;Database=MyDatabase;Trusted_Connection=yes;" />
...works but is less-than ideal because it uses a Trusted Connection rather than a Username/Password combination.

QUESTIONS...

(A) What exactly does the error in Item 4 mean?

(B) Do 4 and 5 imply that one must use a Trusted_Connection for all SQL Server 2005 Express connection strings when the database does not reside in the web application's App_Data folder or use a "Attach a database file" type of connection string?

(C) Are there any alternatives?

(D) What do you suggest?

Please advise.

Thank you.

-- Mark Kamoski

Hi Mark,

Here are the answers to your questions:

(A). The error message means a client connecting to SQL Server may encounter this named pipe error when connecting to SQL Server if the server has not enabled named pipe support even though other protocols such as TCP/IP are available.

(B). You are not required to use a Trusted_Connection if you have enabled SQL Authentication on the SQL Server.

(C)& (D) I would suggest you to try the connection again after a while. If that doesn't help and you're always getting this error, please check the following articles for troubleshoot.

http://msdn2.microsoft.com/en-us/library/ms175496.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx
http://blogs.msdn.com/sql_protocols/archive/2005/12/22/506607.aspx

Connection Strings

I have created a SSIS package, and got it to perform as I want.

I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.

If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.

Here is the connection string that works:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase

Here is the connection string that fails:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase

The strange thing is that when I use the Connection Manager dialog screen and click on "Test Connection", I get the response that the connection succeeded. It is only when I try to run the task that I get an error.

Here is the error I am getting:

[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.

[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.

I have eliminated the obvious errors (incorrect Userid or password). Also, I am unable to use Integrated Security as this package needs to be distributed to various systems that may or may not be on our company's primary domain.

It seems I am missing something really basic here, but am not seeing it.

Any thoughts?

Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||

Has this ever worked for you? Yes, using integrated security

Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.

Are you using package configurations? No

I think the key here is your second point. I created a new package, and the connection now works. So, the question is how do I fix my original package? I'm not really thrilled about creating a brand new package being that this one is quite complicated.

Suggestions?

|||Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.|||

WRBehning,

Welcome to the new world of SSIS! I have had similar problems, especially when you copy and paste items. Basically I think the internal Ids in SSIS get messed up somehow. Alot of times if you delete and re-add an item it fixes the problem. Doesn't give me great confidence when an "enterprise solution" has so many strange problems. Good Luck! (to us all)

|||

WRBehning wrote:

Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

If you have a RFE (Request for Enhancement) then file it at http://connect.microsoft.com with a detailed write-up.

Only thru doing this will SSIS get closer to being the product that people want it to be.

-Jamie

|||

WRBehning wrote:

Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

Can you explain exactly what the problem was in the original. Its not clear from this?

If its something that people need to know then I'd like to add it here: http://blogs.conchango.com/jamiethomson/archive/2006/10/18/SSIS_3A00_-Random-information-for-beginners.aspx

Thanks

-Jamie

|||The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.|||

WRBehning wrote:

The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.

That's worrying if it didn't work. However I have previously had no problems with changing connection strings (for that is what we're talking about here).

One thing that can cause problems is if (for example) the ServerName property doesn't marry up with the server name that you are setting in the ConenctioNString property although in your case the only difference is in authentication mode so I shouldn't expect it to be a problem.

I've also tried your repro steps as above and didn't experience any problems.

What version/service pack are you on?

-Jmie

|||

Here you go...

A couple of things I should mention.

I tried deleting and re-creating the connections and this did not solve the problem.

The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.

SQLExpress (SQL Server 9.0.2047)

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

|||

WRBehning wrote:

Here you go...

A couple of things I should mention.

I tried deleting and re-creating the connections and this did not solve the problem.

The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.

SQLExpress (SQL Server 9.0.2047)

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Seems we're on the same. Strange.

Oh well. Let's chalk it up to experience. If it happens again, let us know.

Thanks

Jamie

|||

I am experiencing the same behaviour.

The package was first created using EncryptWithUserKey setting, and the connection credentials was for a trusted connection to a SQL Server.

We changed the package security to use EncryptWithPassword, and the connection credentials stayed the same and continued to work properly.

When we changed the connection credentials to use a Standard SQL login, I would set the login and password and check the "Remember password" option. The Test Connection button was successful. Then after closing the connection manager properties, I would immediately reopen the properties and the password was gone, but the checkbox was still there, and the Test Connection would fail.

Mike

Connection Strings

I have created a SSIS package, and got it to perform as I want.

I am having a problem though with connecting to my data source (OLE DB Source) using SQL Server Authentication.

If I use Integrated security, I have no problems. If I use SQL Server Authentication, I get errors.

Here is the connection string that works:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Integrated Security=SSPI;Initial Catalog=MyDataBase

Here is the connection string that fails:

Provider=SQLNCLI.1;Data Source=.\SqlExpress;Persist Security Info=True;Password=**********;User ID=myUserid;Initial Catalog=MyDataBase

The strange thing is that when I use the Connection Manager dialog screen and click on "Test Connection", I get the response that the connection succeeded. It is only when I try to run the task that I get an error.

Here is the error I am getting:

[OLE DB Source [1]] Error: The AcquireConnection method call to the connection manager "MyDataBase" failed with error code 0xC0202009.

[DTS.Pipeline] Error: component "MyDataBase" (1) failed validation and returned error code 0xC020801C.

I have eliminated the obvious errors (incorrect Userid or password). Also, I am unable to use Integrated Security as this package needs to be distributed to various systems that may or may not be on our company's primary domain.

It seems I am missing something really basic here, but am not seeing it.

Any thoughts?

Has this ever worked for you? Are you able to create a brand new package and it still fails? Are you using package configurations?|||

Has this ever worked for you? Yes, using integrated security

Are you able to create a brand new package and it still fails? No, actually I tried a new simple package, and it works.

Are you using package configurations? No

I think the key here is your second point. I created a new package, and the connection now works. So, the question is how do I fix my original package? I'm not really thrilled about creating a brand new package being that this one is quite complicated.

Suggestions?

|||Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.|||

WRBehning,

Welcome to the new world of SSIS! I have had similar problems, especially when you copy and paste items. Basically I think the internal Ids in SSIS get messed up somehow. Alot of times if you delete and re-add an item it fixes the problem. Doesn't give me great confidence when an "enterprise solution" has so many strange problems. Good Luck! (to us all)

|||

WRBehning wrote:

Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

If you have a RFE (Request for Enhancement) then file it at http://connect.microsoft.com with a detailed write-up.

Only thru doing this will SSIS get closer to being the product that people want it to be.

-Jamie

|||

WRBehning wrote:

Well, thanks to R.K.S. response, I created a brand new package, this time setting the connections to use SQL Server authentication from the beginning, and it fixed my issue. But what a PIA!!! I spent way too much time researching and trying to figure out the problem, and never did find what is was, nor how to fix it. There must be a better way.

Can you explain exactly what the problem was in the original. Its not clear from this?

If its something that people need to know then I'd like to add it here: http://blogs.conchango.com/jamiethomson/archive/2006/10/18/SSIS_3A00_-Random-information-for-beginners.aspx

Thanks

-Jamie

|||The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.|||

WRBehning wrote:

The issue I had was that I created the SSIS package using Windows Authentication for my OLEDB connections. After I had completed the package, I tried to switch to SQL Server Authentication and even though the "Test Connection" responded with "Test Connection Succeeded", the package would not run. Finally, like I stated earlier, I created a new package, using Sql Server Authentication from the beginning, and the issue was resloved.

That's worrying if it didn't work. However I have previously had no problems with changing connection strings (for that is what we're talking about here).

One thing that can cause problems is if (for example) the ServerName property doesn't marry up with the server name that you are setting in the ConenctioNString property although in your case the only difference is in authentication mode so I shouldn't expect it to be a problem.

I've also tried your repro steps as above and didn't experience any problems.

What version/service pack are you on?

-Jmie

|||

Here you go...

A couple of things I should mention.

I tried deleting and re-creating the connections and this did not solve the problem.

The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.

SQLExpress (SQL Server 9.0.2047)

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

|||

WRBehning wrote:

Here you go...

A couple of things I should mention.

I tried deleting and re-creating the connections and this did not solve the problem.

The connections are connecting to SQL Express, not standard SQL, though I do not see where this would be a consideration.

SQLExpress (SQL Server 9.0.2047)

Microsoft Visual Studio 2005
Version 8.0.50727.42 (RTM.050727-4200)
Microsoft .NET Framework
Version 2.0.50727

Installed Edition: Professional

Microsoft Visual Basic 2005 77626-009-0000007-41520
Microsoft Visual Basic 2005

Microsoft Visual C# 2005 77626-009-0000007-41520
Microsoft Visual C# 2005

Microsoft Visual C++ 2005 77626-009-0000007-41520
Microsoft Visual C++ 2005

Microsoft Visual J# 2005 77626-009-0000007-41520
Microsoft Visual J# 2005

Microsoft Visual Web Developer 2005 77626-009-0000007-41520
Microsoft Visual Web Developer 2005

Crystal Reports AAC60-G0CSA4B-V7000AY
Crystal Reports for Visual Studio 2005

SQL Server Analysis Services
Microsoft SQL Server Analysis Services Designer
Version 9.00.2047.00

SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.2047.00

SQL Server Reporting Services
Microsoft SQL Server Reporting Services Designers
Version 9.00.2047.00

Seems we're on the same. Strange.

Oh well. Let's chalk it up to experience. If it happens again, let us know.

Thanks

Jamie

|||

I am experiencing the same behaviour.

The package was first created using EncryptWithUserKey setting, and the connection credentials was for a trusted connection to a SQL Server.

We changed the package security to use EncryptWithPassword, and the connection credentials stayed the same and continued to work properly.

When we changed the connection credentials to use a Standard SQL login, I would set the login and password and check the "Remember password" option. The Test Connection button was successful. Then after closing the connection manager properties, I would immediately reopen the properties and the password was gone, but the checkbox was still there, and the Test Connection would fail.

Mike

connection string based CREATE CUBE supported in AS 2005.

Hi,

I am trying to use the CREATECUBE functionality in AS 2005 through
connection string property, but getting following error:

Microsoft OLE DB Provider for Analysis Services 2005:
The following system error occurred: Unspecified error .

csSourceDSN=PROVIDER=MSOLAP;DATASOURCE=WOTTRANSUBHSXP\DEV;INITIAL
CATALOG=National;

CREATE CUBE [National] (
DIMENSION [Line],
LEVEL [All Line] TYPE ALL,
LEVEL [Line],
LEVEL [Brand],
LEVEL [Item Name],
DIMENSION [Date],
LEVEL [All Date] TYPE ALL,
LEVEL [Year] TYPE YEAR,
LEVEL [Quarter] TYPE QUARTER,
LEVEL [Month] TYPE MONTH,
DIMENSION [Market],
LEVEL [All Market] TYPE ALL,
LEVEL [Market],
DIMENSION [State],
LEVEL [All State] TYPE ALL,
LEVEL [State],
LEVEL [Outlet],
MEASURE [Quantity] FUNCTION SUM FORMAT '#,#',
MEASURE [Cost] FUNCTION SUM FORMAT 'Standard',
MEASURE [Revenue] FUNCTION SUM FORMAT 'Standard'
)

INSERT INTO [National](
[Line].[Line],
[Line].[Brand],
[Line].[Item Name],
[Date].[Year],
[Date].[Quarter],
[Date].[Month],
[Market].[Market],
[State].[State],
[State].[Outlet],
[Measures].[Quantity],
[Measures].[Cost],
[Measures].[Revenue]
)
OPTIONS ATTEMPT_ANALYSIS
SELECT
[National].[Line:Line],
[National].[Line:Brand],
[National].[Line:Item Name],
[National].[Date:Year],
[National].[Date:Quarter],
[National].[Date:Month],
[National].[Market:Market],
[National].[State:State],
[National].[State:Outlet],
[National].[Measures:Quantity],
[National].[Measures:Cost],
[National].[Measures:Revenue]
FROM [National]
WHERE [Line:Line] = 'Microwaves'
AND [Date:Year] = '1994'

I also tried using CREATE GLOBAL CUBE statement:
"CREATE GLOBAL CUBE [National123] Storage 'C:\\National1.cub' FROM
[National] ( MEASURE [National].[Quantity], DIMENSION
[National].[Line] ( LEVEL [Line], LEVEL [Brand], LEVEL [Item
Name] ) )";

Any idea if we can still use CREATECUBE & INSERTINTO properties in AS
2005 or we need to switch to CREATE GLOBAL CUBE?

Any help in this regard would be appreciated.

Thanks,
Santosh.

Hi Santosh,

No, you can't use this syntax to create a local cube from an AS2005 server cube any more. The CREATE GLOBAL CUBE syntax will work, as will using XMLA to create your local cube.

Chris

|||

Hi Chris,

Has this thing been documented somewhere on msdn?

I need a reference in order to put in my document, which would substantiate this change.

Thanks,
Santosh.

|||

No, the only place that it's documented as far as I know is the chapter on local cubes in 'MDX Solutions' second edition, which I updated from the first edition. I got the information that CREATE CUBE is no longer supported direct from the dev team.

Chris

|||Thanks Chris. Even this reference is good enough for me.

Connection String - Does not conform to the OLE DB specification

I'm trying to build a connection string to SQL Server 7.0 from ASP.net w/ C#

I get the following error:
Format of the initialization string does not conform to the OLE DB specification. Starting around char[100] in the connection string.

What the heck does this mean? What am I doing wrong.. My connection string is below:

string strConnection = "Provider='Provider=SQLOLEDB; server=XXXXXX.XXXXXXXXXXXXX.COM;'UID=XXXXXX;PWD=XXXXXXX;DATABASE=XXXXXX'";

Is there a way to make good connection strings like a tool or something?

Thanks for your time.
thunkYou can add OleDbConnection control from toolbox to your form in Visual Studio .NET project .
Then go to properties -> ConnectionString and choose <New Connection...>
You will get a tool to make connection string and test connection.

Also, you can use Server Explorer (View -> Server Explorer) on the same way.|||A good reference for connection string information can be found athttp://www.connectionstrings.com.

Terri

Connection Problem using the SQLClient Driver

I can create a Data Source in Visual Studio (BIDS) using the OLE DB Provider for Analysis Services 9.0 Provider without error. However, when I try to use the .NET SqlClient Provider, I cannot access any databases running under Analysis Services.

With the .NET Provider selected, I enter the server name. When I go to select a database name, only my SQL Server Databases populate the drop down list. If I manually enter the Analysis Server dB, I get a log in error.

Is there some configuration I need to set to allow the .NET Driver access to my Analysis Services databases?

Use ADOMD.NET .NET object model to access Analysis Services.

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

connection problem MSSQL SERVER & PWS same machine

Im getting an error when i try to connect to my MS SQL database

0x80040e21 ... multiple-step ole db operation generated errors ...check each ole db status value

this code works connecting to database via web hosting, only things i changed was to replace the server with "(local)" [also tried ip no joy there either] and add integrated security to the connection string

ms sql server and IIS, personal web server all on same laptop, i can access the same database with same details no problem to login it gives up on the subsequent login

code (generally)

Set objconn=Server.CreateObject("ADODB.Connection")
objconn.ConnectionString="SERVER=(local);Database=blah;uid=blah1;pwd=blah2;Integrated Security=true;"

objconn.open

can anybody help

ta, bIf you are using Driver={SQL Server} then instead use the native OLEDB connection style of

Provider=SQLOLEDB.1;UID=user;Password=password;Initial Catalog=DBName;Data Source=Servername

Then try your code again.

Check the following URL:

http://www.adopenstatic.com/faq/80040e21.asp|||thanks om but im afraid i still havent got it working :( had seen that link already but thank u

i have tried all concievable options at this stage ?? eg

http://www.tnsites.com/support/s_databaseconn.asp#SQL

Set objConn = Server.CreateObject("ADODB.Connection")
objConn.open "Driver={SQL Server};Provider=SQLOLEDB.1;SERVER=136.xxx.xxx.xxx;DSN=localhostname;UID=uuu;PWD=ppp;Initial Catalog=bmdb; Integrated Security=true"

Error Type:
Provider (0x80040E21)
Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
/DotNetNuke/jobid/sel_services.asp, line 12

Any further suggestions?

I have no problem hooking up to same database in the web.config file --

<add key="connectionString" value="Server=136.xxx.xxx.xxx;Database=bmdb;uid=uuu;pwd=ppp;Integrated Security=true;" /
--

AND it worked previously on the web4life internet hosting server --

Set objConn=Server.CreateObject("ADODB.Connection")
objConn.ConnectionString="DRIVER={SQL Server};SERVER=xxx.xxxxx.com;Database=bmdb;uid=uuu;pwd=ppp"
objConn.open

--

hosted on the local machine browsing locally
STILL ERROR (0x80040E21)

B|||...

asp or asp.net? and pws? <add key=.. shows it's asp.net, but you're using normal ado. i'm confused.|||ive just started asp.net, so the best I can say is that its an asp.net vb project running on a (pws) personal web server

its no wonder your confused seeing as im confused|||... pws? I'm still borked out on this. I didn't know ASP.NET can run on PWS.

First of all, if you're using an ado connection object like that, then you're better off using an ADO based connection string. Secondly, if you use .net, you should research ado.net under the System.Data namespace.