IUSR Web Access to DB - Separate Servers

I have NT SQL 7 and Web Server on same box. I have a new server with W2K and SQL 2000 installed (no IIS). I am migrating the databases over and when done I will install W2K on the old box and it will remain the IIS Web server front end to the new SQL 2000 Server.

On the old configuration, IIS and SQL 7 on the same box, I added the IUSER to the database from the local computer users list when needed for web access. How do I add that user now that the boxes are seperate? The acccout is not a local account on the new machine and the account is a loca account on the other machine so it does not authenticate to the domain so I can't pull it in from there.

Thanks for any help.

--Steve

ssantos@.csuchico.eduSimple answer is to use SQL Authentication.

Create a SQL user on your SQL box, then use a non-SSPI connection in your ASP/ASPX.

More complicated, but ultimately better answer:
Create a new domain user, give it the same permissions on the IIS machine as the IUSER, restrict it's permissions elsewhere on the domain, then add them as a database user in the SQL box.

ITW Errors

Hi,
I'm trying to use the ITW for one of our German servers. I have created an
input file using Profiler that captures the SQL:BatchCompleted and the
RPC:Completed events. When I run the ITW using the input file I recieve the
following error:
"The workload does not contain any events or queries that can be tuned
against the current database. Check to see that the trace contains valid
events or that the SQL script contains valid queries and you are tuning
against the right database"
If I select only certain tables to analyze I recieve the following error:
"There are no events in the workload. Either the trace file contained no
SQL batch or RPC events or the SQL script contained no SQL queries.
I have run a broad trace and a narrow trace using the specific database id
as a filter.
Both using a file and a table return the same errors.
If I use the Query Analyzer Selection option with the ITW with a specific
query from the input file then the ITW does work properly. Also, the size
of the input file is < 100 rows (just a test at this point).
It looks as though the ITW has an issue with the code of one or more of the
statements in the input file. Is this an accurate assumption? Does anyone
know how to resolve this issue so that I can use ITW with many statements as
opposed to using only a few at a time?
Thanks
Jerry
Jerry Spivey wrote:
> Hi,
> I'm trying to use the ITW for one of our German servers. I have
> created an input file using Profiler that captures the
> SQL:BatchCompleted and the RPC:Completed events. When I run the ITW
> using the input file I recieve the following error:
> "The workload does not contain any events or queries that can be tuned
> against the current database. Check to see that the trace contains
> valid events or that the SQL script contains valid queries and you
> are tuning against the right database"
> If I select only certain tables to analyze I recieve the following
> error:
> "There are no events in the workload. Either the trace file
> contained no SQL batch or RPC events or the SQL script contained no
> SQL queries.
> I have run a broad trace and a narrow trace using the specific
> database id as a filter.
> Both using a file and a table return the same errors.
> If I use the Query Analyzer Selection option with the ITW with a
> specific query from the input file then the ITW does work properly.
> Also, the size of the input file is < 100 rows (just a test at this
> point).
> It looks as though the ITW has an issue with the code of one or more
> of the statements in the input file. Is this an accurate assumption?
> Does anyone know how to resolve this issue so that I can use ITW with
> many statements as opposed to using only a few at a time?
> Thanks
> Jerry
There used to be a problem with SQL Server 7.0 with running the ITW on a
client PC using a different locale than the one on the server. Have you
tried running the ITW on the server itself (off-hours)?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||David,
I saw the KB article that referenced that issue but it looked as though it
was fixed in SP1 of Version 7. We're running SP3 of Version 2000. I used
the client utilities from a separate client machine here in the states. I
had a colleague remote desktop to the SQL Server itself running the tools on
the local SQL Server and he received the same errors that I'm getting.
Jerry
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:uMu8ZbIjFHA.3784@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
> There used to be a problem with SQL Server 7.0 with running the ITW on a
> client PC using a different locale than the one on the server. Have you
> tried running the ITW on the server itself (off-hours)?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
|||Jerry Spivey wrote:
> David,
> I saw the KB article that referenced that issue but it looked as
> though it was fixed in SP1 of Version 7. We're running SP3 of
> Version 2000. I used the client utilities from a separate client
> machine here in the states. I had a colleague remote desktop to the
> SQL Server itself running the tools on the local SQL Server and he
> received the same errors that I'm getting.
> Jerry
>
Have you examined the contents of the workload file to see what was
actually captured? If so, what happens if you copy one of the commands
and tune is manually from Query Analyzer. Does it work? How many
workload queries did you tell the ITW to examine in the workload file?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Yea that is my approach right now. I'm copy and pasting individual
statements into QA using the QAS option. Haven't found the culprit yet -
about 90 left to go.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eOlxUkIjFHA.2904@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
> Have you examined the contents of the workload file to see what was
> actually captured? If so, what happens if you copy one of the commands and
> tune is manually from Query Analyzer. Does it work? How many workload
> queries did you tell the ITW to examine in the workload file?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
sql

ITW Errors

Hi,
I'm trying to use the ITW for one of our German servers. I have created an
input file using Profiler that captures the SQL:BatchCompleted and the
RPC:Completed events. When I run the ITW using the input file I recieve the
following error:
"The workload does not contain any events or queries that can be tuned
against the current database. Check to see that the trace contains valid
events or that the SQL script contains valid queries and you are tuning
against the right database"
If I select only certain tables to analyze I recieve the following error:
"There are no events in the workload. Either the trace file contained no
SQL batch or RPC events or the SQL script contained no SQL queries.
I have run a broad trace and a narrow trace using the specific database id
as a filter.
Both using a file and a table return the same errors.
If I use the Query Analyzer Selection option with the ITW with a specific
query from the input file then the ITW does work properly. Also, the size
of the input file is < 100 rows (just a test at this point).
It looks as though the ITW has an issue with the code of one or more of the
statements in the input file. Is this an accurate assumption? Does anyone
know how to resolve this issue so that I can use ITW with many statements as
opposed to using only a few at a time?
Thanks
JerryJerry Spivey wrote:
> Hi,
> I'm trying to use the ITW for one of our German servers. I have
> created an input file using Profiler that captures the
> SQL:BatchCompleted and the RPC:Completed events. When I run the ITW
> using the input file I recieve the following error:
> "The workload does not contain any events or queries that can be tuned
> against the current database. Check to see that the trace contains
> valid events or that the SQL script contains valid queries and you
> are tuning against the right database"
> If I select only certain tables to analyze I recieve the following
> error:
> "There are no events in the workload. Either the trace file
> contained no SQL batch or RPC events or the SQL script contained no
> SQL queries.
> I have run a broad trace and a narrow trace using the specific
> database id as a filter.
> Both using a file and a table return the same errors.
> If I use the Query Analyzer Selection option with the ITW with a
> specific query from the input file then the ITW does work properly.
> Also, the size of the input file is < 100 rows (just a test at this
> point).
> It looks as though the ITW has an issue with the code of one or more
> of the statements in the input file. Is this an accurate assumption?
> Does anyone know how to resolve this issue so that I can use ITW with
> many statements as opposed to using only a few at a time?
> Thanks
> Jerry
There used to be a problem with SQL Server 7.0 with running the ITW on a
client PC using a different locale than the one on the server. Have you
tried running the ITW on the server itself (off-hours)?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David,
I saw the KB article that referenced that issue but it looked as though it
was fixed in SP1 of Version 7. We're running SP3 of Version 2000. I used
the client utilities from a separate client machine here in the states. I
had a colleague remote desktop to the SQL Server itself running the tools on
the local SQL Server and he received the same errors that I'm getting.
Jerry
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:uMu8ZbIjFHA.3784@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
>> Hi,
>> I'm trying to use the ITW for one of our German servers. I have
>> created an input file using Profiler that captures the
>> SQL:BatchCompleted and the RPC:Completed events. When I run the ITW
>> using the input file I recieve the following error:
>> "The workload does not contain any events or queries that can be tuned
>> against the current database. Check to see that the trace contains
>> valid events or that the SQL script contains valid queries and you
>> are tuning against the right database"
>> If I select only certain tables to analyze I recieve the following
>> error:
>> "There are no events in the workload. Either the trace file
>> contained no SQL batch or RPC events or the SQL script contained no
>> SQL queries.
>> I have run a broad trace and a narrow trace using the specific
>> database id as a filter.
>> Both using a file and a table return the same errors.
>> If I use the Query Analyzer Selection option with the ITW with a
>> specific query from the input file then the ITW does work properly. Also,
>> the size of the input file is < 100 rows (just a test at this
>> point).
>> It looks as though the ITW has an issue with the code of one or more
>> of the statements in the input file. Is this an accurate assumption?
>> Does anyone know how to resolve this issue so that I can use ITW with
>> many statements as opposed to using only a few at a time?
>> Thanks
>> Jerry
> There used to be a problem with SQL Server 7.0 with running the ITW on a
> client PC using a different locale than the one on the server. Have you
> tried running the ITW on the server itself (off-hours)?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||Jerry Spivey wrote:
> David,
> I saw the KB article that referenced that issue but it looked as
> though it was fixed in SP1 of Version 7. We're running SP3 of
> Version 2000. I used the client utilities from a separate client
> machine here in the states. I had a colleague remote desktop to the
> SQL Server itself running the tools on the local SQL Server and he
> received the same errors that I'm getting.
> Jerry
>
Have you examined the contents of the workload file to see what was
actually captured? If so, what happens if you copy one of the commands
and tune is manually from Query Analyzer. Does it work? How many
workload queries did you tell the ITW to examine in the workload file?
--
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Yea that is my approach right now. I'm copy and pasting individual
statements into QA using the QAS option. Haven't found the culprit yet -
about 90 left to go.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eOlxUkIjFHA.2904@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
>> David,
>> I saw the KB article that referenced that issue but it looked as
>> though it was fixed in SP1 of Version 7. We're running SP3 of
>> Version 2000. I used the client utilities from a separate client
>> machine here in the states. I had a colleague remote desktop to the
>> SQL Server itself running the tools on the local SQL Server and he
>> received the same errors that I'm getting.
>> Jerry
> Have you examined the contents of the workload file to see what was
> actually captured? If so, what happens if you copy one of the commands and
> tune is manually from Query Analyzer. Does it work? How many workload
> queries did you tell the ITW to examine in the workload file?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

ITW Errors

Hi,
I'm trying to use the ITW for one of our German servers. I have created an
input file using Profiler that captures the SQL:BatchCompleted and the
RPC:Completed events. When I run the ITW using the input file I recieve the
following error:
"The workload does not contain any events or queries that can be tuned
against the current database. Check to see that the trace contains valid
events or that the SQL script contains valid queries and you are tuning
against the right database"
If I select only certain tables to analyze I recieve the following error:
"There are no events in the workload. Either the trace file contained no
SQL batch or RPC events or the SQL script contained no SQL queries.
I have run a broad trace and a narrow trace using the specific database id
as a filter.
Both using a file and a table return the same errors.
If I use the Query Analyzer Selection option with the ITW with a specific
query from the input file then the ITW does work properly. Also, the size
of the input file is < 100 rows (just a test at this point).
It looks as though the ITW has an issue with the code of one or more of the
statements in the input file. Is this an accurate assumption? Does anyone
know how to resolve this issue so that I can use ITW with many statements as
opposed to using only a few at a time?
Thanks
JerryJerry Spivey wrote:
> Hi,
> I'm trying to use the ITW for one of our German servers. I have
> created an input file using Profiler that captures the
> SQL:BatchCompleted and the RPC:Completed events. When I run the ITW
> using the input file I recieve the following error:
> "The workload does not contain any events or queries that can be tuned
> against the current database. Check to see that the trace contains
> valid events or that the SQL script contains valid queries and you
> are tuning against the right database"
> If I select only certain tables to analyze I recieve the following
> error:
> "There are no events in the workload. Either the trace file
> contained no SQL batch or RPC events or the SQL script contained no
> SQL queries.
> I have run a broad trace and a narrow trace using the specific
> database id as a filter.
> Both using a file and a table return the same errors.
> If I use the Query Analyzer Selection option with the ITW with a
> specific query from the input file then the ITW does work properly.
> Also, the size of the input file is < 100 rows (just a test at this
> point).
> It looks as though the ITW has an issue with the code of one or more
> of the statements in the input file. Is this an accurate assumption?
> Does anyone know how to resolve this issue so that I can use ITW with
> many statements as opposed to using only a few at a time?
> Thanks
> Jerry
There used to be a problem with SQL Server 7.0 with running the ITW on a
client PC using a different locale than the one on the server. Have you
tried running the ITW on the server itself (off-hours)?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||David,
I saw the KB article that referenced that issue but it looked as though it
was fixed in SP1 of Version 7. We're running SP3 of Version 2000. I used
the client utilities from a separate client machine here in the states. I
had a colleague remote desktop to the SQL Server itself running the tools on
the local SQL Server and he received the same errors that I'm getting.
Jerry
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:uMu8ZbIjFHA.3784@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
> There used to be a problem with SQL Server 7.0 with running the ITW on a
> client PC using a different locale than the one on the server. Have you
> tried running the ITW on the server itself (off-hours)?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com|||Jerry Spivey wrote:
> David,
> I saw the KB article that referenced that issue but it looked as
> though it was fixed in SP1 of Version 7. We're running SP3 of
> Version 2000. I used the client utilities from a separate client
> machine here in the states. I had a colleague remote desktop to the
> SQL Server itself running the tools on the local SQL Server and he
> received the same errors that I'm getting.
> Jerry
>
Have you examined the contents of the workload file to see what was
actually captured? If so, what happens if you copy one of the commands
and tune is manually from Query Analyzer. Does it work? How many
workload queries did you tell the ITW to examine in the workload file?
David Gugick
Quest Software
www.imceda.com
www.quest.com|||Yea that is my approach right now. I'm copy and pasting individual
statements into QA using the QAS option. Haven't found the culprit yet -
about 90 left to go.
"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:eOlxUkIjFHA.2904@.tk2msftngp13.phx.gbl...
> Jerry Spivey wrote:
> Have you examined the contents of the workload file to see what was
> actually captured? If so, what happens if you copy one of the commands and
> tune is manually from Query Analyzer. Does it work? How many workload
> queries did you tell the ITW to examine in the workload file?
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I se
e
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\Sql
Setup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directo
ry
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......
Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>
|||Here is the last portion of the log.
.....
.....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\ scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>
>

Issues with 2000 SP4 Upgrade.

I have two servers now, which I am getting the same issue. The servers are
Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
through copying files and then says "Initializing Server for Upgrade". I see
that the server starts but nothing happens......Hi
What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
say ?
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom" <Tom@.discussions.microsoft.com> wrote in message
news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
>I have two servers now, which I am getting the same issue. The servers are
> Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> through copying files and then says "Initializing Server for Upgrade". I
> see
> that the server starts but nothing happens......
>
>|||Here is the last portion of the log.
....
....
14:03:17 End Action: CreateRegistrySetSQL
14:03:17 Begin Action: RegWriteSetupEntry
14:03:17 End Action: RegWriteSetupEntry
14:03:17 *** Unable to get RegisteredOwner to apply to Serial number
14:03:17 Begin Action: CreateSer
14:03:17 End Action: CreateSer
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\setup.iss returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for returned: 3, 3
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlsp.log returned: 0, 0
14:03:17 SetFileSecuritySQLAndAdmin for C:\WINNT\sqlstp.log returned: 0, 0
14:03:17 SetFileSecPerfAndLogUsers for C:\Program Files\Microsoft SQL
Server\MSSQL\Binn\SQLCTR80.DLL returned: 1332, 1332
14:03:17 Begin ServPriv (MSSQLSERVER)
14:03:17 End ServPriv()
14:03:18 Upgrading databases
14:03:18 Upgrading databases on instance 'MSSQLSERVER'
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 6 -Service MSSQLSERVER
14:03:18 Process Exit Code: (0)
14:03:18 C:\DOCUME~1\SQL_SE~1\LOCALS~1\Temp\2\SqlSetup\Bin\scm.exe -Silent
1 -Action 1 -Service MSSQLSERVER -StartupOptions \-T4022 \-T4010 \-m
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> What does your log file "sqlsp.log" in your c:\windows or c:\winnt directory
> say ?
> --
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Tom" <Tom@.discussions.microsoft.com> wrote in message
> news:996FEBDC-FC3B-4FEF-A052-E764A080E419@.microsoft.com...
> >I have two servers now, which I am getting the same issue. The servers are
> > Windows 2000 O/S. The SQL Servers were at 760 version. The setup gets
> > through copying files and then says "Initializing Server for Upgrade". I
> > see
> > that the server starts but nothing happens......
> >
> >
> >
>
>

Issues running DTS Packages

Hello,

I have a sql 2005 cluster. I recently moved a new server in place of an old server we had

Both the servers now have w2k3 sp2 sql 2005 sp1 both have 2000 dts designer package.

My problem is that i have a dts package that runs on sql01\inst01 without any issues but the same package when i try to run it from sql02\inst02 just hangs ... digging deeper i found that - when i try to parse a query / build query / try giving parameters in a Execute SQL task it says

"The selected connection does not provide sql support"

The connection it reference is a postgres connection looking up info from a udl file.

I am not sure what is missing.

Any help is appreciated as soon as possible...

Resolved. Thanks

Issue with a remote report server

Hey guys,

I have three servers, assume ServerA,ServerB, and ServerC. ServerA is where the database(datasource) is located. ServerB is used as a report server and Server C is my local machine where I design reports. So obviously I deployed the reports from my local machine(server C) to the remote report server(server B). Deployement was successful but I got the following error when I run the report from the report server. You might think that the report is not pointing to the right data source, I checked that several times and it is pointing to the right data source.

An error has occurred during report processing. (rsProcessingAborted)

Cannot create a connection to data source 'dsCallB'. (rsErrorOpeningConnection)

For more information about this error navigate to the report server on the local server machine, or enable remote errors

However, I also observed that when I deployed the same reports on the local machine report server(server C), it run with out any problem. So it seems that the problem is related with the remote server(server B) not the data source.

Does anybody has a solution for this.

Thx

Normally it is one of two things when I encounter this message:

1) The report is not connected to the datasource on ServerB (as you mentioned).

2) The DataSource Connection String on ServerB has a misspelling somewhere. (If ServerA is Case Sensitive Collation, check upper/lower case).

If not those, make sure ServerB can connect to the database on ServerA through some other means (ODBC, etc). Good luck.

|||

Well, the quick and easy solution is to change the configuration for the connection already deployed to ServerB. Since it's working from your local PC/ServerC, so just use your ID and password to config the connection on ServerB. But if ServerB is really a production server, it's better to create a separate logon, either a Windows account or a SQL account with the access to ServerA. Make sure to set the password to never expire. Then use this account to config the connection on ServerB. HTH.

|||I don't think I need to config the connection on ServerB, because, there are other several reports deployed and run with out any problem. FYI the existing reports was actually deployed by some body else. This problem happened for the new reports that I developed. It is very weired situation.|||

The problem has to be with the connection from ServerB to the data source, otherwise you wouldn't be able to run it from your local machine.

Are you using a shared data source?

Go to the properties of the report in Report Manager, and select 'Data Sources' from the left. Select 'A custom data source' and verify Microsoft SQL Server is listed in your 'Connection type'. The 'Connection string' should look like this: Data Source=ServerA;Initial Catalog=DB_Name. Select 'Credentials stored securely in the report server' and type your username (domain\user) and your password. Then check the box 'Use as Windows credentials when connecting to the data source' and hit Apply at the bottom.

If you do this from ServerB (RS Server), then you should get an informative error message if/when you get the error. Do you have access to log directly into ServerB?

Jarret

|||

Hey Jarret,

First, I really appreciate your follow up to assist me in solving this issue.

Actually, I am using a shared data source to generate the reports. As a matter of fact, the existing reports also uses a shared data source and run with out any problem. I also tried what you said up here, however, I got the same error message. Anyhow, I just wanna cross check one thing with you. If I select A custom data source, which server's username and password do I have to apply, ServerA(datasource), ServerB(report server), or ServerC(Local machine)?

Thx.

|||

I really don't mind. Actually, I'm sorry that I haven't been able to get you a solution yet.

If you select 'A custom data source', then the connection string will have to point to your database server (ServerA) and you'll have to supply either a SQL account or a windows account (domain\user) that has permission to read the data.

If this still doesn't work, I would start a new report without using the shared data source and just store the connection information into the report itself.

Jarret

|||

The problem maybe because the shared datasource you are using may be in a different folder on your report manager whereas you would have specified a different targetdatasourcefolder (Report project properties) for your report. So, it is trying to create that data source at runtime and not able to do it because you dont have enough permissions.

Shyam

|||

I'm very disappointed with this annoying error message. I experienced the same kind of problem in some other project and I was able to solve it with no time. One thing which makes me angry is that the existing shared data sources are working fine, however the data source that I created doesn't work. I wasted a lot of time on this. I don't know what to do next. May be go for a vacation LOL.

Anyhow I will let you know if I am able to find something new. Please keep on posting me if you have any idea.

Thx.

|||

Have you read my post and any progress?

Shyam

|||

Hi Shyam,

I checked that too. On my project properties, the TargetDataSourceFolder is 'Data Sources'. On the report manager, the data sources are created in the same folder name, i.e. 'Data Sources'. I couldn't see any problem.

I even created a new data source (which is not a shared data source) on the report server level and pointed it to my report, but still getting the same error message

|||

Maybe the following links will be of some help to you:

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

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=288600&SiteID=17

Shyam

isqlw connection problems

I'm trying to connect to remote sql servers. I can connect to and work with
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Conn
ect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne SheffieldFYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does n
ot exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Co
nnect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql[vbcol=seagreen]
>

isqlw connection problems

I'm trying to connect to remote sql servers. I can connect to and work with
the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it times
out trying to connect with the error messages:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
Followed by:
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
Why can't I connect with Query Analyzer, but I can with Enterprise Manager?
How do I resolve this?
I have no problems using Query Analyzer and connecting to my local sql
servers.
I have no problems using Query Analyzer to connect to local and remote sql
servers on my other computer, just with this one computer.
Thanks,
Wayne Sheffield
FYI: I did check out http://support.microsoft.com/?kbid=328306, but nothing
there helped out.
Thanks,
Wayne
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Are you using the same account as EM uses?
Andrew J. Kelly SQL MVP
"Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> I'm trying to connect to remote sql servers. I can connect to and work
with
> the servers in EM. But, when I click on "Tools|SQL Query Analyzer", it
times
> out trying to connect with the error messages:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> Followed by:
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect())
> Why can't I connect with Query Analyzer, but I can with Enterprise
Manager?
> How do I resolve this?
> I have no problems using Query Analyzer and connecting to my local sql
> servers.
> I have no problems using Query Analyzer to connect to local and remote sql
> servers on my other computer, just with this one computer.
> Thanks,
> Wayne Sheffield
>
|||Yes. When you open QA this way, it uses the EM account settings.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:uiF7z8daEHA.2840@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Are you using the same account as EM uses?
> --
> Andrew J. Kelly SQL MVP
>
> "Wayne Sheffield" <wayne_sheffield@.hotmail.com> wrote in message
> news:OB2MF3caEHA.2812@.TK2MSFTNGP11.phx.gbl...
> with
> times
or[vbcol=seagreen]
> Manager?
sql
>