ETL from multiple Access databases -SSIS?

Howdy Folks,

I have an ETL project that I want to ask a question about. I want to loop through a folder containing several Access databases, and extract and load each one into a single SQL Server 2005 database. The table layout is the same for all the Access dbs, as well as the SQL db. The number of Access dbs in the folder, their records, and their names will change. Is there a way i can use the SSIS Foreach tool to move through the folder and set the connection string inside the loop?

Thanks for your reply,

Chris

Yes, you can do this.

Use the ForEach File Enumerator to enumerate your list of files. you can use wildcards (e.g. *.mdb)

Store the file path of each file in a variable. You can then use the contents of that variable to dynamically build your connection string using an expression.

Lots of information via Google about this stuff if you want to go hunting or ask here with any pertinent questions.

Regards

-Jamie

|||

Thanks Jamie (alot ) for your suggestion. I tried using the Foreach File Enumerator with the root path for the Access files and a *.mdb wildcard. Then I created a mapped string variable varFileNameto hold the file path. Inside the loop i have my Data Flow Task. In the data source for the task, I was using the variable in an expression as the ConnectionSting property which didn't work. So I added an OLE DB connection string in the expression like "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" + @.[User::varFileName] but i don't think that's the answer.

I've been googling on this but can't find solutions for multiple .mdb's, most of waht i find is dealing with flat files. Great blogs btw.

|||

Should be able to find all you need here: http://www.connectionstrings.com/

-Jamie

|||

Yep, i went there. Thanks Jamie. My string was ok. Actually what got me running was to set the Foreach Loop Container>Properties>Execution>DelayValidation = True. Works great running the SSIS package on the box with SQL server (as opposed to OLE DB) destinations.

Error-Unable to get report parameters:Unable to access Web Service

Hi - In our RS + SP1 installation on Windows Server 2003, we recently began
to get the following error:
"Unable to get report parameters: Unable to access Web Service: The request
failed with HTTP status 403: Forbidden."
We are calling Render() in code using an account which has admin rights to
the RS box, is not locked out, etc. Event logs show no failures and the RS
logs are as useless as ever. I see no access denieds from Windows auditing
either.
Thoughts?
thanks muchHi,
Thanks for your posting!
From your descriptions, I understood that you are not able to access Web
Service with the error message "Unable to get report parameters: Unable to
access Web Service: The request failed with HTTP status 403: Forbidden."
Have I understood you? Correct me if I was wrong.
Based on my knowledge, it seems that "anonymous" for Reportserver virual
folder is enabled. Please try the following steps and let me know whether
it works
1. Right click ReportServer in IIS->Properties->Directory Security
2. Make sure "Intergrated Windows authentication" is checked and "enable
anonymouse access" is unchecked.
Thank you for your patience and corporation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael, I looked at my anonymous setting but it was set properly.
By chance, I tried to execute http://server/reportserver/reportservice.asmx
and it said that there were no permissions to execute scripts in this virtual
root. Sure enough, I looked at the ReportServer virtual root config and the
Execute permissions were improperly set. Not sure how changed, but once I
put it back to "Scripts and Executables" I was good.
Thanks much
"Michael Cheng [MSFT]" wrote:
> Hi,
> Thanks for your posting!
> From your descriptions, I understood that you are not able to access Web
> Service with the error message "Unable to get report parameters: Unable to
> access Web Service: The request failed with HTTP status 403: Forbidden."
> Have I understood you? Correct me if I was wrong.
> Based on my knowledge, it seems that "anonymous" for Reportserver virual
> folder is enabled. Please try the following steps and let me know whether
> it works
> 1. Right click ReportServer in IIS->Properties->Directory Security
> 2. Make sure "Intergrated Windows authentication" is checked and "enable
> anonymouse access" is unchecked.
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hi,
Thanks for your prompt updates!
It's great to hear that it did turn out to be an authority issue and you
yourself have resolved it.
Thank you for your patience and corporation. If you have any questions or
concerns on SQL Server, don't hesitate to let me know. We are always here
to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.sql

Errors while upsizing Access database to SQLS2k

I am trying to upsize an Access database to SQL Server 2000. I select
"Create new database" option.
I select "LOCAL" as the database. and check [x] use trusted connection.
SQL server is on this local machine. I supply a name for the new
database and click [Next>] and I get the following error.
================================================== ===============
Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access denied.
================================================== ===============
Why am I getting these errors?
SQL Server is installed to accept mixed mode (or Windows authentication
mode)
SQL Server is running.
VS.Net Professional is loaded on this system so an ODBC driver should
be available.
What steps, other than I am taking should I be doing?
Are you doing this on the machine that MSDE is running on? If you are trying
to do this remotely then you will not be able to connect to the database
server, since you supplied DISABLENETWORKPROTOCOLS=1 as a parameter to your
installation. Also since you installed a named instance you will need to
supply the full name to the instance, which in your case will be <your
machine name>\HipMSDE. (local) will not work as the database server name, as
it will try to connect to a server with only the same name as the machine
and not the named instance.
Jim
"dbuchanan" <dbuchanan52@.hotmail.com> wrote in message
news:1107749903.811964.185300@.g14g2000cwa.googlegr oups.com...
>I am trying to upsize an Access database to SQL Server 2000. I select
> "Create new database" option.
> I select "LOCAL" as the database. and check [x] use trusted connection.
> SQL server is on this local machine. I supply a name for the new
> database and click [Next>] and I get the following error.
> ================================================== ===============
> Connection failed:
> SQLState: '01000'
> SQL Server Error: 53
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
> (Connect()).
> Connection failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access denied.
> ================================================== ===============
> Why am I getting these errors?
> SQL Server is installed to accept mixed mode (or Windows authentication
> mode)
> SQL Server is running.
> VS.Net Professional is loaded on this system so an ODBC driver should
> be available.
> What steps, other than I am taking should I be doing?
>
|||Jim,
Thank you for your reply.
When I changed the name to the name of my computer "SEDNA", it worked!
I thought "(local)" was the proper name to use because the upsizing
wizard offered it in the list. I thought it "discovered" that name, and
after all the name in Enterprize manager is "(local)" not "SEDNA". Now
that you let me in on this sectret, I know. Thank you for tell me the
other scret, that I can upsize to MSDE using "SEDNA\HipMSDE". There is
know whay I could have guessed this!
This all frustrates me very much! How am I supposed to know to use
"SEDNA" rather than "(local)" when "(local)" is offered to me in the
list? and Enterprize manager does not use "SEDNA"? How am I supposed to
know the sintax "SEDNA\HipMSDE" when that is NOT offered in the list?
How am I supposed to know the secret code "SEDNA\HipMSDE"? Nothing
anywhere tells me this sintax!!?!

> it will try to connect to a server with only the same name as the
machine
> and not the named instance
Where the #%$* am I supposed to discover this! I've been reading these
instructions for two days!!!?! I have not seen anything even hinting to
this.
Why does the system mislead me and accept "(local)" under othere
contexts such as VB.NET connection strings. It was the VB.NET
connection string context that lead me to guess "SEDNA" because that
works in a connection string even though the name of the instance is
NOT!!!! "SEDNA", its the name of the machine.
Where do I learn all these mysteries?
Doug
Jim Young wrote:
> Are you doing this on the machine that MSDE is running on? If you are
trying
> to do this remotely then you will not be able to connect to the
database
> server, since you supplied DISABLENETWORKPROTOCOLS=1 as a parameter
to your
> installation. Also since you installed a named instance you will need
to
> supply the full name to the instance, which in your case will be
<your
> machine name>\HipMSDE. (local) will not work as the database server
name, as
> it will try to connect to a server with only the same name as the
machine[vbcol=seagreen]
> and not the named instance.
> Jim
> "dbuchanan" <dbuchanan52@.hotmail.com> wrote in message
> news:1107749903.811964.185300@.g14g2000cwa.googlegr oups.com...
select[vbcol=seagreen]
connection.[vbcol=seagreen]
exist[vbcol=seagreen]
authentication[vbcol=seagreen]
should[vbcol=seagreen]
|||hi,
dbuchanan wrote:
> This all frustrates me very much! How am I supposed to know to use
> "SEDNA" rather than "(local)" when "(local)" is offered to me in the
> list? and Enterprize manager does not use "SEDNA"? How am I supposed
> to know the sintax "SEDNA\HipMSDE" when that is NOT offered in the
> list? How am I supposed to know the secret code "SEDNA\HipMSDE"?
> Nothing anywhere tells me this sintax!!?!
>.....
http://msdn.microsoft.com/library/de...setup_2xmb.asp
you can download BOL (BookOnLine) from
http://www.microsoft.com/sql/techinf...2000/books.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

Errors Upsizing an access 2002 Database to SQL server 2005

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

MrKim wrote:

I have an Access DB with about 50 tables. When I run the upsize wizard all bur four tables import beautifully, data and all. Four of the tables fail with the message 'Table was skipped, or export failed'

When I try to IMPORT the data I get 100 or so messages like this one:

Warning 0x80047076: Data Flow Task: The output column "AssessPlanPHPID" (23) on output "OLE DB Source Output" (11) and component "Source - tblAssessPlan" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
(SQL Server Import and Export Wizard)

And the import fails. Note that the upsize creates the tables just fine, it just won't import the data.

Any ideas?

I apologize for the fonts jumping around.

Regrading the 4 tables that fail; Are you sure you don't have other errors? 'Table was skipped, or export failed' Is not clear enough

The other message is just a warning telling you that at some point a certain column in the dataflow is not used anymore; the intention is to suggest to remove it if it is no necessary....only you can answer that question.

|||

No, that is is. When you use the Access upsizing wizard that is all the info it gives on the report. More useful maybe is the error messages given when trying to import the data through SQL server. I did finally import the data. There were bad dates which had to be fixed first.

I did it by turning of the SQL atuonumber/Prim Key, then writing a progam to import one record at a time, and noting the ID on the ones that fail - they all had bad dates.

sql

Errors on Datasource.aspx page

I have an installation of RS 2000 on a Win 2003 server.
I've started getting an error whenever I access the Data Source pages
using the Report Manager.
The page loads OK. But I cannot make any changes. For example, if I try
to change the "Connect Using" options from "Windows Integrated
Secuirty" to "Credentials stored securely ...", the radio button shows
the selection, but the required text boxes are not enabled, In the
bottom left corener of the IE status bar, "Error on Page" flashes.
The server log files and event logs show nothing regarding the error.
This happens on all Data Source pages on this server.

Any ideas?

It sounds like some of the javascript files are missing. Try reregistering asp.net client files by running aspnet_regiis -c from \windows\microsoft.net\framework\v1.1.4322.

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and am
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
--
Paul G
Software engineer.sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:
>Hi I am trying to give database access to a second database for a user and am
>getting the error (Error 21002 username allready exists). Anyhow seems that
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Hi thanks for the response. the error I am getting now is 15023 user or role
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
--
Paul G
Software engineer.
"Hari Prasad" wrote:
> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> > Hi I am trying to give database access to a second database for a user and
> > am
> > getting the error (Error 21002 username allready exists). Anyhow seems
> > that
> > I ran into the problem before and ran a command from query analyzer and it
> > seemed to fix it. Anyhow can not remember the command I used.
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>|||it worked, thanks.
--
Paul G
Software engineer.
"Hari Prasad" wrote:
> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> > Hi I am trying to give database access to a second database for a user and
> > am
> > getting the error (Error 21002 username allready exists). Anyhow seems
> > that
> > I ran into the problem before and ran a command from query analyzer and it
> > seemed to fix it. Anyhow can not remember the command I used.
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and a
m
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
--
Paul G
Software engineer.sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:

>Hi I am trying to give database access to a second database for a user and
am
>getting the error (Error 21002 username allready exists). Anyhow seems tha
t
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.|||Hi thanks for the response. the error I am getting now is 15023 user or rol
e
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch wi
th
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>|||it worked, thanks.
--
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch wi
th
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>

Error21002 user name already exists

Hi I am trying to give database access to a second database for a user and am
getting the error (Error 21002 username allready exists). Anyhow seems that
I ran into the problem before and ran a command from query analyzer and it
seemed to fix it. Anyhow can not remember the command I used.
thanks.
Paul G
Software engineer.
sp_dropuser?
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.
|||Sounds like it may have been sp_change_users_login
See books online for details.
-Sue
On Wed, 17 Aug 2005 16:39:01 -0700, "Paul"
<Paul@.discussions.microsoft.com> wrote:

>Hi I am trying to give database access to a second database for a user and am
>getting the error (Error 21002 username allready exists). Anyhow seems that
>I ran into the problem before and ran a command from query analyzer and it
>seemed to fix it. Anyhow can not remember the command I used.
>thanks.
|||Hi,
U are searching for this
exec sp_addrolemember N'db_datareader', N'username
hope this helps u
from]
killer'
|||Hi,
Seems that SID for the existing user inside the database is in mismatch with
Login inside syslogins. So goahead and use the
system stored procedure sp_change_users_login (see books online) as Sue
pointed out to fix the mis match.
Thanks
Hari
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
> Hi I am trying to give database access to a second database for a user and
> am
> getting the error (Error 21002 username allready exists). Anyhow seems
> that
> I ran into the problem before and ran a command from query analyzer and it
> seemed to fix it. Anyhow can not remember the command I used.
> thanks.
> --
> Paul G
> Software engineer.
|||Hi thanks for the response. the error I am getting now is 15023 user or role
already exists in the current database when I tried to give database access
of a second database to the user. I tried the sp_change_users_login
'AUTO_FIX','username' command. I am able to give the user access to one
dbase but not the other.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>
|||it worked, thanks.
Paul G
Software engineer.
"Hari Prasad" wrote:

> Hi,
> Seems that SID for the existing user inside the database is in mismatch with
> Login inside syslogins. So goahead and use the
> system stored procedure sp_change_users_login (see books online) as Sue
> pointed out to fix the mis match.
> Thanks
> Hari
> SQL Server MVP
>
>
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:2E83131E-CB3C-4824-882B-2DE85A6B6975@.microsoft.com...
>
>

Error: Subreport could not be shown

I am getting this error when I run this report only when I access this report
from my PC. When I run it on the server it works fine. Any idea.
ThanksOn Jun 13, 11:14 am, Shan <S...@.discussions.microsoft.com> wrote:
> I am getting this error when I run this report only when I access this report
> from my PC. When I run it on the server it works fine. Any idea.
> Thanks
Is the subreport located in the correct location on your PC? Also,
sometimes this error occurs when there is an error in the subreport.
Is there maybe some missing data/stored procedure/etc on your local
machine that does exist on the other machine/server? Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks for the tip. But all of a sudden it's working now. I dint' do any
thing. I dont know why wouldn't it run I never had this issue before. Thanks
"EMartinez" wrote:
> On Jun 13, 11:14 am, Shan <S...@.discussions.microsoft.com> wrote:
> > I am getting this error when I run this report only when I access this report
> > from my PC. When I run it on the server it works fine. Any idea.
> > Thanks
> Is the subreport located in the correct location on your PC? Also,
> sometimes this error occurs when there is an error in the subreport.
> Is there maybe some missing data/stored procedure/etc on your local
> machine that does exist on the other machine/server? Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Jun 13, 1:32 pm, Shan <S...@.discussions.microsoft.com> wrote:
> Thanks for the tip. But all of a sudden it's working now. I dint' do any
> thing. I dont know why wouldn't it run I never had this issue before. Thanks
> "EMartinez" wrote:
> > On Jun 13, 11:14 am, Shan <S...@.discussions.microsoft.com> wrote:
> > > I am getting this error when I run this report only when I access this report
> > > from my PC. When I run it on the server it works fine. Any idea.
> > > Thanks
> > Is the subreport located in the correct location on your PC? Also,
> > sometimes this error occurs when there is an error in the subreport.
> > Is there maybe some missing data/stored procedure/etc on your local
> > machine that does exist on the other machine/server? Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
I'm glad it works now. In this case, I would suggest checking the
query/stored procedure that is sourcing the subreport to make sure
that it does not have performance problems (probably via the Database
Engine Tuning Advisor). Also, check the report using a full range of
parameter values (where applicable) to verify that you did not omit
the error by parameter selection. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant

Error: SQL Server does not exist or access denied. (Error code 17).

Hello everyone.

I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:

dataserver is running sbs2003 sql2003 and analsys services.

server2 is running server2003 is to be the application server for project.

ProjectDb is the database that i have setup in sql.

username is the account that can control everything as administrer.

in Sharepoint is asks for the database server: <<dataserver>>

SQL Server database name: <<ProjectDb>>

I'm using windoes authentication and then i click ok, and get the error message.

I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.

Any help would be great.

Thanks

Everett Buel

Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||

SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.

But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.

Data services are all running on both servers.

Thanks for your reply

Everett Buel

|||

It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.

Bryce

Error: SQL Server does not exist or access denied. (Error code 17).

Hello everyone.

I am trying to install Project Server, and i'm having issues with sharepoint, and connecting to SQL:

dataserver is running sbs2003 sql2003 and analsys services.

server2 is running server2003 is to be the application server for project.

ProjectDb is the database that i have setup in sql.

username is the account that can control everything as administrer.

in Sharepoint is asks for the database server: <<dataserver>>

SQL Server database name: <<ProjectDb>>

I'm using windoes authentication and then i click ok, and get the error message.

I've also see the error message can not find the SQL Server, and access denied. Under ODBC i have installed the sql server information under System DSN.

Any help would be great.

Thanks

Everett Buel

Start by confirming that SQL Server is running and that you can access it directly. I take it this is SQL Server 2000, so you should have Query Analyzer installed and you can use it to try to connect to your database. Also (more basic) check to confirm that the SQL Server service is started.|||

SQL is running I have the Query Analyzer installed. All services are started. I can access the Sql Server from my desktop so i know that part is working.

But when I try to start up the data connection of the sharepoint services on the server running server 2003 i still get the error message.

Data services are all running on both servers.

Thanks for your reply

Everett Buel

|||

It would be nice if you two finished this thread. I can't tell you how many times I've gone searching the MS web site for resolution of error messages only to find this type of non-solution. If this is all you can do then why don't you delete the useless thread.

Bryce

Error: Server Error in '/ReportServer' Application.

I get the following error when going to http://localhost/reportserver, I did try what it recommended but it did't work.

Error:

Failed to access IIS metabase.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904.
Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[HostingEnvironmentException: Failed to access IIS metabase.] System.Web.Configuration.MetabaseServerConfig.MapPathCaching(String siteID, VirtualPath path) +3492186 System.Web.Configuration.MetabaseServerConfig.System.Web.Configuration.IConfigMapPath.MapPath(String siteID, VirtualPath vpath) +9 System.Web.Hosting.HostingEnvironment.MapPathActual(VirtualPath virtualPath, Boolean permitNull) +163 System.Web.CachedPathData.GetConfigPathData(String configPath) +382 System.Web.CachedPathData.GetConfigPathData(String configPath) +243 System.Web.CachedPathData.GetApplicationPathData() +68 System.Web.CachedPathData.GetVirtualPathData(VirtualPath virtualPath, Boolean permitPathsOutsideApp) +3385695 System.Web.Configuration.RuntimeConfig.GetLKGRuntimeConfig(VirtualPath path) +189

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42Can you access other asp.net applications on the same website, and running under the same app pool (if you are on IIS6) or the ASP.NET process account (if you are on IIS5.1)?|||

Not sure. I am trying to set up the report server so that I can start creating SSRS and report builder stuff off a 1 box before I create live on the server using the backend DB tables of our internal tools.

I am on communicator if you can chat for a few...this has had me going crazy for a few days.

Also ASPNET_REGIIS.exe is not recognized.

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:

> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:
> >> Any suggestions
> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM|||You can use Server Network Utility to set the tcp port for the sql instance.
--
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote:
>> >> Any suggestions
>> Oh the usual:
>> 1. Check to make sure that they are using the right username/password
>> combination.
>> 2. Make sure the client is not behind a firewall that prevents comm
>> over the SQL Server port.
>> 3. Make sure the same applies for the server.
>> 4. Make sure that they are using the right authentication type (sql or
>> win).
>> 5. Make sure that the server is configured to use the right auth mode.
>> 6. Make sure that the server's host name appears in the list of
>> available server to connect to (see 2 & 3).
>> HTH
>> AM
>>

Error: Server doesnot exist or Access denied

We are host with windows 2003 server and SQL 2000 DB server. Our clients are
trying to connect to their individual databases using SQL webadmin or
Enterprise manager tool and they get the following message:
"SQL server doesnot exist or access denied.
ConnectionOpen(Connect())"
This is the message from SQL enterprise manager. The workstation is XP SP1.
Any suggestions
>> Any suggestions
Oh the usual:
1. Check to make sure that they are using the right username/password
combination.
2. Make sure the client is not behind a firewall that prevents comm
over the SQL Server port.
3. Make sure the same applies for the server.
4. Make sure that they are using the right authentication type (sql or
win).
5. Make sure that the server is configured to use the right auth mode.
6. Make sure that the server's host name appears in the list of
available server to connect to (see 2 & 3).
HTH
AM
|||Actually we found out that the SQL is not listening on any TCP/IP port but
only listening to named pipes. Any idea of how to make SQL Server listen to
any tcp/ip ports?
"AM" wrote:

> Oh the usual:
> 1. Check to make sure that they are using the right username/password
> combination.
> 2. Make sure the client is not behind a firewall that prevents comm
> over the SQL Server port.
> 3. Make sure the same applies for the server.
> 4. Make sure that they are using the right authentication type (sql or
> win).
> 5. Make sure that the server is configured to use the right auth mode.
> 6. Make sure that the server's host name appears in the list of
> available server to connect to (see 2 & 3).
> HTH
> AM
>
|||In Enterprise Manager, right click on the DB, select properties. In
ther dialog box, int he General tab, on the bottom click on Network
configuration. In the dialog box that pops up, in the general tab,
check to see if TCP/IP is listed on the box on the right. If not select
it from the box on the left and click on enable. YOu can edit the
properties to set up the port to listen on.
HTH
AM
|||You can use Server Network Utility to set the tcp port for the sql instance.
-oj
"Snehal Rana" <SnehalRana@.discussions.microsoft.com> wrote in message
news:E263310C-BB72-483D-BE16-DA854F38CB40@.microsoft.com...[vbcol=seagreen]
> Actually we found out that the SQL is not listening on any TCP/IP port but
> only listening to named pipes. Any idea of how to make SQL Server listen
> to
> any tcp/ip ports?
>
> "AM" wrote: