Does anyone know how I can get the hotfix for 830466?
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.
You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Showing posts with label contact. Show all posts
Showing posts with label contact. Show all posts
Monday, February 27, 2012
Hotfix needed
Does anyone know how I can get the hotfix for 830466?
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
--
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
--
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Hotfix needed
Does anyone know how I can get the hotfix for 830466?
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
The kb article (http://support.microsoft.com/?kbid=830466)
says to contact microsoft customer service. When I ask for
free online support it asks for the product id. When I try
to check where the pid is, it's not listed. Our licenseing
folks have no idea what our pid is for sql server.You can find the product ID in the registry key
HKLM\Software\Microsoft\Microsoft SQL Server\80\Registration\ProductID
Jacco Schalkwijk
SQL Server MVP
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.|||You can get a newer fix (878), which includes the fixes for 852, here:
http://support.microsoft.com/?kbid=838166
http://www.aspfaq.com/
(Reverse address to reply.)
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:387301c46a86$d7ba28c0$3a01280a@.phx.gbl...
> Does anyone know how I can get the hotfix for 830466?
> The kb article (http://support.microsoft.com/?kbid=830466)
> says to contact microsoft customer service. When I ask for
> free online support it asks for the product id. When I try
> to check where the pid is, it's not listed. Our licenseing
> folks have no idea what our pid is for sql server.
Hotfix from KB821334
What happened to the hotfix required by Reporting Services for SQL Server
2000 SP3a? It looks like you have to contact PSS to get any hotfixes
anymore. Does that mean anyone new to Reporting Services has to contact PSS
just to be able to install Reporting Services?Well, that's what we had to do.
--
Adrian M.
MCP
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?|||Good question. Hotfix 859 is required if installing on Windows 2003 Server
(which means almost everybody needs it). I'll ask this in the SQL Server MVP
forum and see what is up and provide the answer on this thread.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
PSS
> just to be able to install Reporting Services?|||My investigation (not official from MS) shows that most documentation has
been updated to refer to SP4 (which would have this hotfix rolled up in it).
So could be that SP4 will be soon and that would be what people would apply
instead of the hotfix. For now, contacting PSS seems to be the only route to
take.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?
2000 SP3a? It looks like you have to contact PSS to get any hotfixes
anymore. Does that mean anyone new to Reporting Services has to contact PSS
just to be able to install Reporting Services?Well, that's what we had to do.
--
Adrian M.
MCP
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?|||Good question. Hotfix 859 is required if installing on Windows 2003 Server
(which means almost everybody needs it). I'll ask this in the SQL Server MVP
forum and see what is up and provide the answer on this thread.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
PSS
> just to be able to install Reporting Services?|||My investigation (not official from MS) shows that most documentation has
been updated to refer to SP4 (which would have this hotfix rolled up in it).
So could be that SP4 will be soon and that would be what people would apply
instead of the hotfix. For now, contacting PSS seems to be the only route to
take.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Tim Paulsen" <Tim Paulsen@.discussions.microsoft.com> wrote in message
news:4B6D804D-435C-4810-A200-913E5A744322@.microsoft.com...
> What happened to the hotfix required by Reporting Services for SQL Server
> 2000 SP3a? It looks like you have to contact PSS to get any hotfixes
> anymore. Does that mean anyone new to Reporting Services has to contact
> PSS
> just to be able to install Reporting Services?
Subscribe to:
Posts (Atom)