Problem with SQL Service Pack 4

You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:[vbcol=seagreen]
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make i
t
>stick (assuming you have the system database backups just in case you need
>to regress)
>|||I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
install says it completed but after I rebooted and did a select @.@.version it
still shows SP3. I only have a default instance so I know that it installed
on the right instance. Could anyone help me out with this?|||You can review the setup log for any errors (file called sqlsp.log in the
windows directory). It is perfectly safe to run SP4 again to try and make it
stick (assuming you have the system database backups just in case you need
to regress)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||I tried it several times but got the same result.
I've attached a copy of my sqlsp.log file. I looked at the sqlsp.log file
and it only listed one non-fatal error...I can't see this being the problem
considering it was nonfatal.
Jasper Smith wrote:[vbcol=seagreen]
>You can review the setup log for any errors (file called sqlsp.log in the
>windows directory). It is perfectly safe to run SP4 again to try and make i
t
>stick (assuming you have the system database backups just in case you need
>to regress)
>|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||What does the following query return?
SELECT SERVERPROPERTY('ProductLevel')
Hope this helps.
Dan Guzman
SQL Server MVP
"Leon Parker" <u23479@.uwe> wrote in message news:625d255c1f101@.uwe...
>I upgraded from SQL 2000 Service Pack 3 to SQL 2000 Service Pack 4. The
> install says it completed but after I rebooted and did a select @.@.version
> it
> still shows SP3. I only have a default instance so I know that it
> installed
> on the right instance. Could anyone help me out with this?|||SP3....
Dan Guzman wrote:[vbcol=seagreen]
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200606/1|||SP3....
Dan Guzman wrote:[vbcol=seagreen]
>What does the following query return?
> SELECT SERVERPROPERTY('ProductLevel')
>
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...server/200606/1

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg Pagan
I found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 installation and REPLSYS.SQL

I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
installation has 5 named instances. I was able to install SQLServer SP4
onto 4 of the named instances with out any problem. When I installed the
SP4 update I was logged on as the local administrator and used Windows
authentication.
When I attempted the install on the last instance, it failed running the
REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and it
told me that the error was with procedure sp_addextendedproc in the master
db. The script tried to execute the following command:
sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
The error says that there is already an object named 'xp_mergexpusage' in
the database.
I have looked at the list of extended stored procedures listed in the Master
DB and I cannot see the xp_mergexpusage stored procedure anywhere. Is it
hidden somehow? I can see the stored procedure in the other instances that
were sucessfully updated but not in the instance that fails.
Has anyone else run into this problem when installing SP4?
Is there a way to attempt a delete of the xp_mergexpusage extended stored
procedure incase it is hidden somehow?
Any help would be greatly appreciated.
Greg PaganI found the answer to this issue myself.
Turns out the problem had nothing to do with SP4 at all. It just pointed
out the underlying issue.
I had corruption in the master data base that somehow messed with the
DBI_NextID. The value of that indicator was out of sync with the max(ID)
indicator. The DB_NextID as less than the Max(ID) which was telling the
system that the object already existed. The fix which came from
sqlforums.windowsitpro.com is to generate new DB_NextIDs by creating and
droping simple tables in master until the counter for DB_NextID grows larger
than max(ID). It took me over 700 table creates to get to that point.
After that the SP4 Update ran successfully.
Thanks anyway.
"Greg Pagan" <gpagan@.thehartford.com> wrote in message
news:O%23CHMX3VGHA.5692@.TK2MSFTNGP09.phx.gbl...
>I have a SQLServer 2000 SP3 running on Windows Server 2000 SP4. My
>installation has 5 named instances. I was able to install SQLServer SP4
>onto 4 of the named instances with out any problem. When I installed the
>SP4 update I was logged on as the local administrator and used Windows
>authentication.
> When I attempted the install on the last instance, it failed running the
> REPLSYS.SQL script. After some digging I found the REPLSYS.OUT file and
> it told me that the error was with procedure sp_addextendedproc in the
> master db. The script tried to execute the following command:
> sp_addextendedproc 'xp_mergexpusage', 'xprepl.dll'
> The error says that there is already an object named 'xp_mergexpusage' in
> the database.
> I have looked at the list of extended stored procedures listed in the
> Master DB and I cannot see the xp_mergexpusage stored procedure anywhere.
> Is it hidden somehow? I can see the stored procedure in the other
> instances that were sucessfully updated but not in the instance that
> fails.
> Has anyone else run into this problem when installing SP4?
> Is there a way to attempt a delete of the xp_mergexpusage extended stored
> procedure incase it is hidden somehow?
> Any help would be greatly appreciated.
> Greg Pagan
>
>

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks for
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
Emmanuel
Hello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:

> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behaving
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are there
> any related problems with other tools?
> With kind regards,
> Emmanuel
>
sql

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks fo
r
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
EmmanuelHello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:

> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks
for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I d
id
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behavin
g
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are the
re
> any related problems with other tools?
> With kind regards,
> Emmanuel
>

Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks for
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
EmmanuelHello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:
> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behaving
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are there
> any related problems with other tools?
> With kind regards,
> Emmanuel
>

problem with Selection criteria

Using SS2000 SP4, RS2000, VS2003
I'm trying to put the start date and end date in the report header. I have a
report title in the header now and it prints ok. As soon as I add a text box
and the parameter for the start date, nothing in the report header prints but
the body of the report prints. This is what is in the header
"=FORMAT(Parameters!StartDate.Value, "MMMM d, yyyy")". I also have some
parameters in the report footer and they aren't printing either. I copied
them from another report.
Thanks,
--
Dan D.I can't explain it but all of a sudden it started working in both the header
and the footer.
--
Dan D.
"Dan D." wrote:
> Using SS2000 SP4, RS2000, VS2003
> I'm trying to put the start date and end date in the report header. I have a
> report title in the header now and it prints ok. As soon as I add a text box
> and the parameter for the start date, nothing in the report header prints but
> the body of the report prints. This is what is in the header
> "=FORMAT(Parameters!StartDate.Value, "MMMM d, yyyy")". I also have some
> parameters in the report footer and they aren't printing either. I copied
> them from another report.
> Thanks,
> --
> Dan D.

Problem with 'Reply-To' in data driven subscription

I am running SQL Server 2000 sp4 and Reporting Services 2000 sp2. I set
up a data driven subscription with a static Reply-To address. However,
when the report runs, the reply is the default in the config file.
I've seen 1 other post on this but no solution. Help would be
appreciated.
NeilI captured this info using SQL Profiler:
exec CreateSubscription @.Report_Name =N'/WebInvoiceStatus_Reports/VendorActivity', @.id ='86750772-3D96-4059-8B1E-9F5F5D6C8000', @.OwnerSid =0x01050000000000051500000093E362480D7A5A33828BA628CA300100, @.OwnerName
= N'US\A0312698', @.OwnerAuthType = 1, @.Locale = N'en-US',
@.DeliveryExtension = N'Report Server Email', @.InactiveFlags = 0,
@.ExtensionSettings =N'<ParameterValues><ParameterValue><Name>TO</Name><Field>EmailAddress</Field></ParameterValue><ParameterValue><Name>ReplyTo</Name><Value>aphelp@.abcdef.com</Value>...
This shows that the value I wanted was being picked up. So I wonder if
the problem is with the smtp.
Neil|||My issue is not with the 'Reply-To' I just discovered.
It is the 'From' that I have been trying to change and that cannot be
done for each subscription.
The From did change when I changed it in the config file.
I love solving my own problems.
Neil