Error creating new SSIS project

In my local client installation of the BI tools, I get the following error when simply creating an SSIS project and the default empty Package tries to display on the screen.

Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

I can use the Reporting Services designer with no problems, and I can use SSIS from the client tools on the server. It is just on my local PC that I get this error. I have completely uninstalled all the tools and reinstalled with no luck.

PLEASE HELP!

If anyone can help, please reply. I am unable to use SSIS AT ALL right now because a new package will only display this error message. And this is the purchased version, not the evaluation copy.

Here is the full message

Microsoft Visual Studio is unable to load this document:
Index (zero based) must be greater than or equal to zero and less than the size of the argument list.

|||

I know it looks like I'm being a pest by bumping my post again, but I am not able to use SSIS at all on my PC. I HAVE TO get this resolved.

I am on Windows XP Pro fully patched and updated. I had SQL Express on my PC before and have since uninstalled it to see if that would help.

PLEASE HELP!!!

Error Connecting To SQL 2005 through Webservice using SQL Authentication

Running a SQL 2005 Database under a Default instance. i.e. (SERVERNAME) and not (SERVERNAME/SQL2005)

I have a SQL Login sa password.

When I connect to SQL 2005 from anywhere other then the webservice it works fine.

In my webservice i am using System.Data.SqlClient.

SqlConnection, SqlCommand, SqlDataAdapter are being used to called a stored procedure and return the data into a System.Data.DataSet.

I get the following error when calling DataAdapter.Fill(dataSet);

{"TCP Provider: An existing connection was forcibly closed by the remote host.\r\n\r\nLogin failed for user 'sa'."}

I have no resolutions as of yet. Any help would be greatly appreciated.

Did you mean you can connect to the SQL2005 from anywhere with 'sa' login, except webservice? You can check the status of 'sa' login in management studio under Security->Logins, also make sure the Authentication Mode is SQL Server and Windows.|||

I have checked the status of the login for user "sa" and it has access rights and grant levels to everything it needs to.

I have also created a new account specifically for that database which does not work either. Same error.

And yes my SQL 2005 Instance is configured to use both SQL Authentication and Windows Authentication. (Mixed Mode).

Any Ideas?

|||

If you encountered this issue when you're trying to establish encrypted connection , you may take a look at this article:

http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"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
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?
Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "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
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"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
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "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
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yep...used the Surface Area Configuration and enabled remote logins
with Named Pipes and Support.
But just so that I didn't do anything wrong..what would be the
essential steps here (if you were in my shoes)..?|||Mohd Al Junaibi wrote:
> Yep...used the Surface Area Configuration and enabled remote logins
> with Named Pipes and Support.
> But just so that I didn't do anything wrong..what would be the
> essential steps here (if you were in my shoes)..?
>
Is SQL running on your local workstation, or on a remote server? Can
you ping that remote server, via hostname and via IP address? Is there
a firewall involved?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, both MSSQL Service is running, and the agent is on as well. I
don't recall having the firewall running.
I'm beginning to think it has to do with credentials.
I'm running a command to create my WEBFORMS on a virtual directory,
it's experimental and called "Blinq" from Microsoft.
Anyways...I'll try to check things here..
thanks a million

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"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
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "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
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yep...used the Surface Area Configuration and enabled remote logins
with Named Pipes and Support.
But just so that I didn't do anything wrong..what would be the
essential steps here (if you were in my shoes)..?|||Mohd Al Junaibi wrote:
> Yep...used the Surface Area Configuration and enabled remote logins
> with Named Pipes and Support.
> But just so that I didn't do anything wrong..what would be the
> essential steps here (if you were in my shoes)..?
>
Is SQL running on your local workstation, or on a remote server? Can
you ping that remote server, via hostname and via IP address? Is there
a firewall involved?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, both MSSQL Service is running, and the agent is on as well. I
don't recall having the firewall running.
I'm beginning to think it has to do with credentials.
I'm running a command to create my WEBFORMS on a virtual directory,
it's experimental and called "Blinq" from Microsoft.
Anyways...I'll try to check things here..
thanks a million