unbelievable!
Wow. This is unacceptable. From all my years of working with Microsoft
products, this is the worst installation problem yet. I already asked this
question but didn't get a proper answer. I do not know where else to go but
here, so I'm going to ask this question again
OS: Windows XP Pro service pack 1
SQL: SQL Server 2000 Developer Edition Service Pack 4
IIS: IIS 5.0
.NET Framework: 1.1 Latest service pack
Windows Installer: version 3.1
I am trying to install client reporting services on my system with the above
configurations. It fails...f***ing miserably on the first step (before it
starts installing the actual reporting services). Without a proper
explanation, asside from the fact that it tells me to look at a log file for
the error:
C:\Program Files\Microsoft SQL Server\80\RS Setup Bootstrap\Log\RSSTP_.CAB
So I do that. I open the log file in there. There's whole bunch of cr4p from
the setup written to that log file. I check the bottom of the file where it
failed the installation. Oh, very readable
-- begin error --
<Func Name='DwLaunchMsiExec'>
<Func Name='PerformDetections'>
0
Failed to find property in cache: InstalledInstances
Failed to perform discovery on machine: DC00675
HRESULT: 2147749891
<EndFunc Name='PerformDetections' Return='2' GetLastError='183'>
<Func Name='FSetupLogging'>
<Func Name='CreateSetupLogCabs'>
Creating Setup Logs Cab "C:\Program Files\Microsoft SQL Server\80\RS Setup
Bootstrap\LOG\RSStp_.cab"
-- end error --
Since I noticed the word 'Failed' I assume that the relevant lines would be:
Failed to find property in cache: InstalledInstances
Failed to perform discovery on machine: DC00675
HRESULT: 2147749891
Ok, so I search google:
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2004-17,GGLD:en&q=Failed+to+find+property+in+cache%3A+InstalledInstances+Failed+t
o+perform+discovery+on+machine%3A
Oh am I lucky or what? I get a solution from Microsoft.
http://support.microsoft.com/?kbid=897020
Only one problem. It''s completely f**king useless.my HRESULT: 2147749891 is
not part of the solution
Damn! So I keep searching for the error number 2147749891. Find some minimal
stuff. No fix.
I apologize for the language used. I am tired of trying everything in the
past 3 days to install this. It's a waste of time.
Does anyone have any remote ideas as to maybe, just maybe a way of fixing
this?This is a multi-part message in MIME format.
--=_NextPart_000_0019_01C62248.A69489E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi Leo
I do understand your exasperation
I know what it is when when you feel wholly powerless in front of a =mysterious error message
From the KB article your referenced, I guess it is a WMI problem
It looks like SSRS relies on WMI to enumerates SQL Server instances =installed on this machine
I would try something like this small VBScript to enumerate the =different SQL Server Services running on the localhost machine
Set objWMIService =3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt")
Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each objItem In colItems
WScript.Echo "HostName/ServiceName : " & objItem.HostName & " / " =& objItem.ServiceName
Next
I would say if the script can't enumerate the SQL Server services that =means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo" <none@.none.com> a =E9crit dans le message de news: =eqsApJdIGHA.3408@.TK2MSFTNGP12.phx.gbl...
> Any Microsoft support people that can answer this? This is simply
> unbelievable!
> > > > Wow. This is unacceptable. From all my years of working with Microsoft
> products, this is the worst installation problem yet. I already asked =this
> question but didn't get a proper answer. I do not know where else to =go but
> here, so I'm going to ask this question again
> > OS: Windows XP Pro service pack 1
> SQL: SQL Server 2000 Developer Edition Service Pack 4
> IIS: IIS 5.0
> .NET Framework: 1.1 Latest service pack
> Windows Installer: version 3.1
> > > I am trying to install client reporting services on my system with the =above
> configurations. It fails...f***ing miserably on the first step =(before it
> starts installing the actual reporting services). Without a proper
> explanation, asside from the fact that it tells me to look at a log =file for
> the error:
> > C:\Program Files\Microsoft SQL Server\80\RS Setup =Bootstrap\Log\RSSTP_.CAB
> > So I do that. I open the log file in there. There's whole bunch of =cr4p from
> the setup written to that log file. I check the bottom of the file =where it
> failed the installation. Oh, very readable
> > -- begin error --
> > <Func Name=3D'DwLaunchMsiExec'>
> <Func Name=3D'PerformDetections'>
> 0
> Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> <EndFunc Name=3D'PerformDetections' Return=3D'2' GetLastError=3D'183'>
> <Func Name=3D'FSetupLogging'>
> <Func Name=3D'CreateSetupLogCabs'>
> Creating Setup Logs Cab "C:\Program Files\Microsoft SQL Server\80\RS =Setup
> Bootstrap\LOG\RSStp_.cab"
> > -- end error --
> > Since I noticed the word 'Failed' I assume that the relevant lines =would be:
> > Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> > > Ok, so I search google:
> > =http://www.google.com/search?sourceid=3Dnavclient&ie=3DUTF-8&rls=3DGGLD,G=
GLD:2004-17,GGLD:en&q=3DFailed+to+find+property+in+cache%3A+InstalledInst=ances+Failed+t
> o+perform+discovery+on+machine%3A
> > > Oh am I lucky or what? I get a solution from Microsoft.
> http://support.microsoft.com/?kbid=3D897020
> > Only one problem. It''s completely f**king useless.my HRESULT: =2147749891 is
> not part of the solution
> > Damn! So I keep searching for the error number 2147749891. Find some =minimal
> stuff. No fix.
> > > I apologize for the language used. I am tired of trying everything in =the
> past 3 days to install this. It's a waste of time.
> > Does anyone have any remote ideas as to maybe, just maybe a way of =fixing
> this?
> > >
--=_NextPart_000_0019_01C62248.A69489E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Hi Leo
I do understand your =exasperation
I know what it is when when you feel =wholly powerless in front of a mysterious error message
From the KB article your referenced, I =guess it is a WMI problem
It looks like SSRS relies on WMI to =enumerates SQL Server instances installed on this machine
I would try something like this small =VBScript to enumerate the different SQL Server Services running on the localhost machine
Set objWMIService =3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt") Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each =objItem In colItems WScript.Echo ="HostName/ServiceName : " & objItem.HostName & " / " & =objItem.ServiceName Next
I would say if the script can't =enumerate the SQL Server services that means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo"
--=_NextPart_000_0019_01C62248.A69489E0--|||This is a multi-part message in MIME format.
--=_NextPart_000_000B_01C6225B.35273C90
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Good suggestion and good input. I very much appreciate that. I was =hoping a softie will notice the post and maybe give some more insightful =input. However I have been trying to work out this WMI issue, but =nothing is working so far. Even copying the whole folder from a working =machine and dumping it into mine then re-compiling all the files. =Nothing. However I will take upon your suggestion and try the scripting =to see what happens. Again thank you
Leo
"Med Bouchenafa" <com.hotmail@.bouchenafa> wrote in message =news:eRc6FBkIGHA.3036@.tk2msftngp13.phx.gbl...
Hi Leo
I do understand your exasperation
I know what it is when when you feel wholly powerless in front of a =mysterious error message
From the KB article your referenced, I guess it is a WMI problem
It looks like SSRS relies on WMI to enumerates SQL Server instances =installed on this machine
I would try something like this small VBScript to enumerate the =different SQL Server Services running on the localhost machine
Set objWMIService =3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt")
Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each objItem In colItems
WScript.Echo "HostName/ServiceName : " & objItem.HostName & " / =" & objItem.ServiceName
Next
I would say if the script can't enumerate the SQL Server services that =means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo" <none@.none.com> a =E9crit dans le message de news: =eqsApJdIGHA.3408@.TK2MSFTNGP12.phx.gbl...
> Any Microsoft support people that can answer this? This is simply
> unbelievable!
> > > > Wow. This is unacceptable. From all my years of working with =Microsoft
> products, this is the worst installation problem yet. I already =asked this
> question but didn't get a proper answer. I do not know where else to =go but
> here, so I'm going to ask this question again
> > OS: Windows XP Pro service pack 1
> SQL: SQL Server 2000 Developer Edition Service Pack 4
> IIS: IIS 5.0
> .NET Framework: 1.1 Latest service pack
> Windows Installer: version 3.1
> > > I am trying to install client reporting services on my system with =the above
> configurations. It fails...f***ing miserably on the first step =(before it
> starts installing the actual reporting services). Without a proper
> explanation, asside from the fact that it tells me to look at a log =file for
> the error:
> > C:\Program Files\Microsoft SQL Server\80\RS Setup =Bootstrap\Log\RSSTP_.CAB
> > So I do that. I open the log file in there. There's whole bunch of =cr4p from
> the setup written to that log file. I check the bottom of the file =where it
> failed the installation. Oh, very readable
> > -- begin error --
> > <Func Name=3D'DwLaunchMsiExec'>
> <Func Name=3D'PerformDetections'>
> 0
> Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> <EndFunc Name=3D'PerformDetections' Return=3D'2' =GetLastError=3D'183'>
> <Func Name=3D'FSetupLogging'>
> <Func Name=3D'CreateSetupLogCabs'>
> Creating Setup Logs Cab "C:\Program Files\Microsoft SQL Server\80\RS =Setup
> Bootstrap\LOG\RSStp_.cab"
> > -- end error --
> > Since I noticed the word 'Failed' I assume that the relevant lines =would be:
> > Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> > > Ok, so I search google:
> > =http://www.google.com/search?sourceid=3Dnavclient&ie=3DUTF-8&rls=3DGGLD,G=
GLD:2004-17,GGLD:en&q=3DFailed+to+find+property+in+cache%3A+InstalledInst=ances+Failed+t
> o+perform+discovery+on+machine%3A
> > > Oh am I lucky or what? I get a solution from Microsoft.
> http://support.microsoft.com/?kbid=3D897020
> > Only one problem. It''s completely f**king useless.my HRESULT: =2147749891 is
> not part of the solution
> > Damn! So I keep searching for the error number 2147749891. Find some =minimal
> stuff. No fix.
> > > I apologize for the language used. I am tired of trying everything =in the
> past 3 days to install this. It's a waste of time.
> > Does anyone have any remote ideas as to maybe, just maybe a way of =fixing
> this?
> > >
--=_NextPart_000_000B_01C6225B.35273C90
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Good suggestion and good input. I very =much appreciate that. I was hoping a softie will notice the post and maybe =give some more insightful input. However I have been trying to work out this WMI =issue, but nothing is working so far. Even copying the whole folder from a =working machine and dumping it into mine then re-compiling all the files. =Nothing. However I will take upon your suggestion and try the scripting to see =what happens. Again thank you
Leo
"Med Bouchenafa"
Hi Leo
I do understand your =exasperation
I know what it is when when you feel =wholly powerless in front of a mysterious error message
From the KB article your referenced, =I guess it is a WMI problem
It looks like SSRS relies on WMI to =enumerates SQL Server instances installed on this machine
I would try something like this small =VBScript to enumerate the different SQL Server Services running on the localhost machine
Set objWMIService ==3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt") Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each =objItem In colItems WScript.Echo ="HostName/ServiceName : " & objItem.HostName & " / " & objItem.ServiceName Next
I would say if the script can't =enumerate the SQL Server services that means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo"
--=_NextPart_000_000B_01C6225B.35273C90--|||This is a multi-part message in MIME format.
--=_NextPart_000_0009_01C6226E.DF0AC610
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Arghhhh......horay!
After visiting the MS WMI site and running a plethora of scripts =(similiar to the one you wrote and all returning error codes) I found =something based on one error code (if you try to look at the WMI =properties under the Computer Managment interface it will return "Access =Denied" messages for certain processes. Only if you WMI is somehow =corrupt of course):
http://support.microsoft.com/default.aspx?scid=3Dkb;EN-US;313222
After the default sec. settings were restored, I did a reboot (as usual) =to make sure the changes take place
Put in the Reporting services CD and it all worked. I now have reporting =services
If it was up to me I'd replace 1/2 of the MSs team in charge of =reporting services and installation with you (lol, unless you wouldn't =want that job)
Anyway, it all works now. After losing 3 days I can now start to work.
Thanks for pointing me in the right direction
Note to MS: Regardless of your "we-do-not-care-for-individual-complains =unless it becomes news" attitude, there is still people out there who =care enough to help those in need
I hope one day you will add "HRESULT: 2147749891" to your partial =installation solution already on your site
Leo
"Med Bouchenafa" <com.hotmail@.bouchenafa> wrote in message =news:eRc6FBkIGHA.3036@.tk2msftngp13.phx.gbl...
Hi Leo
I do understand your exasperation
I know what it is when when you feel wholly powerless in front of a =mysterious error message
From the KB article your referenced, I guess it is a WMI problem
It looks like SSRS relies on WMI to enumerates SQL Server instances =installed on this machine
I would try something like this small VBScript to enumerate the =different SQL Server Services running on the localhost machine
Set objWMIService =3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt")
Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each objItem In colItems
WScript.Echo "HostName/ServiceName : " & objItem.HostName & " / =" & objItem.ServiceName
Next
I would say if the script can't enumerate the SQL Server services that =means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo" <none@.none.com> a =E9crit dans le message de news: =eqsApJdIGHA.3408@.TK2MSFTNGP12.phx.gbl...
> Any Microsoft support people that can answer this? This is simply
> unbelievable!
> > > > Wow. This is unacceptable. From all my years of working with =Microsoft
> products, this is the worst installation problem yet. I already =asked this
> question but didn't get a proper answer. I do not know where else to =go but
> here, so I'm going to ask this question again
> > OS: Windows XP Pro service pack 1
> SQL: SQL Server 2000 Developer Edition Service Pack 4
> IIS: IIS 5.0
> .NET Framework: 1.1 Latest service pack
> Windows Installer: version 3.1
> > > I am trying to install client reporting services on my system with =the above
> configurations. It fails...f***ing miserably on the first step =(before it
> starts installing the actual reporting services). Without a proper
> explanation, asside from the fact that it tells me to look at a log =file for
> the error:
> > C:\Program Files\Microsoft SQL Server\80\RS Setup =Bootstrap\Log\RSSTP_.CAB
> > So I do that. I open the log file in there. There's whole bunch of =cr4p from
> the setup written to that log file. I check the bottom of the file =where it
> failed the installation. Oh, very readable
> > -- begin error --
> > <Func Name=3D'DwLaunchMsiExec'>
> <Func Name=3D'PerformDetections'>
> 0
> Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> <EndFunc Name=3D'PerformDetections' Return=3D'2' =GetLastError=3D'183'>
> <Func Name=3D'FSetupLogging'>
> <Func Name=3D'CreateSetupLogCabs'>
> Creating Setup Logs Cab "C:\Program Files\Microsoft SQL Server\80\RS =Setup
> Bootstrap\LOG\RSStp_.cab"
> > -- end error --
> > Since I noticed the word 'Failed' I assume that the relevant lines =would be:
> > Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DC00675
> HRESULT: 2147749891
> > > Ok, so I search google:
> > =http://www.google.com/search?sourceid=3Dnavclient&ie=3DUTF-8&rls=3DGGLD,G=
GLD:2004-17,GGLD:en&q=3DFailed+to+find+property+in+cache%3A+InstalledInst=ances+Failed+t
> o+perform+discovery+on+machine%3A
> > > Oh am I lucky or what? I get a solution from Microsoft.
> http://support.microsoft.com/?kbid=3D897020
> > Only one problem. It''s completely f**king useless.my HRESULT: =2147749891 is
> not part of the solution
> > Damn! So I keep searching for the error number 2147749891. Find some =minimal
> stuff. No fix.
> > > I apologize for the language used. I am tired of trying everything =in the
> past 3 days to install this. It's a waste of time.
> > Does anyone have any remote ideas as to maybe, just maybe a way of =fixing
> this?
> > >
--=_NextPart_000_0009_01C6226E.DF0AC610
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
&
Arghhhh......horay!
After visiting the MS WMI site and =running a plethora of scripts (similiar to the one you wrote and all =returning error codes) I found something based on one error code (if you try to =look at the WMI properties under the Computer Managment interface it will return ="Access Denied" messages for certain processes. Only if you WMI is somehow =corrupt of course):
After the default sec. settings were =restored, I did a reboot (as usual) to make sure the changes take place
Put in the Reporting services CD =and it all worked. I now have reporting services
If it was up to me I'd replace 1/2 of =the MSs team in charge of reporting services and installation with you (lol, unless =you wouldn't want that job)
Anyway, it all works now. After losing =3 days I can now start to work.
Thanks for pointing me in the right direction
Note to MS: Regardless of your "we-do-not-care-for-individual-complains unless it becomes news" =attitude, there is still people out there who care enough to help those in =need
I hope one day you will add ="HRESULT: 2147749891" to your partial installation solution already on your site
Leo
"Med Bouchenafa"
Hi Leo
I do understand your =exasperation
I know what it is when when you feel =wholly powerless in front of a mysterious error message
From the KB article your referenced, =I guess it is a WMI problem
It looks like SSRS relies on WMI to =enumerates SQL Server instances installed on this machine
I would try something like this small =VBScript to enumerate the different SQL Server Services running on the localhost machine
Set objWMIService ==3D =GetObject("winmgmts:\\localhost\root\Microsoft\SqlServer\ComputerManageme=nt") Set colItems =3D objWMIService.ExecQuery("SELECT * FROM SqlService")
For Each =objItem In colItems WScript.Echo ="HostName/ServiceName : " & objItem.HostName & " / " & objItem.ServiceName Next
I would say if the script can't =enumerate the SQL Server services that means you have a problem with WMI
If so, this may lead you to another direction.
Med Bouchenafa
"Leo"
--=_NextPart_000_0009_01C6226E.DF0AC610--
No comments:
Post a Comment