IE Scripts and Printing Error

hi i am using the RSS 2000 version with the service pack 2. it all works fine in my development machine and other test machines in the office but when i take it out into the real world and try to print IE says it cant run some scripts. i have checked the ie security settings and tried enabling all scripts and still the report viewer insists it cant run some scripts and gives me an error. does any one know where i can change settings to enable my reports to print? the computers i am working on are under a domain with its own security settings i know nothing about but if there is anything i can change on the client machine's IE configuration to enable scripts specific to reporting services to run that will be good to know.
ah.. finally found some old posts that talked about this in this forum. finally all fixed up thanks to google search. damned forum search didn't turn up anything. grrrrr!!!
|||Can you please share where you found this information? I, too, have been looking for a solution and have been unsuccessful so far. Thanks|||I am facing similar problem, when print button is pressed, from a modal dialog window, i get an error 0x80004005 which states "Error occurred while printing", when I press OK, I get the IE script error, I am calling the report into a modal dialog window from an ASP page. I have Windows 2000 sp 4, IE 6.0 (no SP applied.)|||The problem was solved after installation of an older version of Windows 2000 Server. One thing is clear that there is a need to look into the reporting services, it is having so many bugs and since last one year microsoft has released no service pack for it. There is no proper support for it.sql

IE Scripts and Printing Error

hi i am using the RSS 2000 version with the service pack 2. it all works fine in my development machine and other test machines in the office but when i take it out into the real world and try to print IE says it cant run some scripts. i have checked the ie security settings and tried enabling all scripts and still the report viewer insists it cant run some scripts and gives me an error. does any one know where i can change settings to enable my reports to print? the computers i am working on are under a domain with its own security settings i know nothing about but if there is anything i can change on the client machine's IE configuration to enable scripts specific to reporting services to run that will be good to know.
ah.. finally found some old posts that talked about this in this forum. finally all fixed up thanks to google search. damned forum search didn't turn up anything. grrrrr!!!
|||Can you please share where you found this information? I, too, have been looking for a solution and have been unsuccessful so far. Thanks|||I am facing similar problem, when print button is pressed, from a modal dialog window, i get an error 0x80004005 which states "Error occurred while printing", when I press OK, I get the IE script error, I am calling the report into a modal dialog window from an ASP page. I have Windows 2000 sp 4, IE 6.0 (no SP applied.)|||The problem was solved after installation of an older version of Windows 2000 Server. One thing is clear that there is a need to look into the reporting services, it is having so many bugs and since last one year microsoft has released no service pack for it. There is no proper support for it.

Identying all installed SQL Server instances on a machine

I think I would use the SQL-DMO object to find SQL instances, then
filter that list to just the single computer you want to query. =20
Ref: http://www.sqlteam.com/item.asp?ItemID=3D5403
Good luck,
Tony Sebion
--Original Message--
From: Volcano [mailto:Volcano@.discussions.microsoft.com]=20
Posted At: Wednesday, August 03, 2005 11:55 AM
Posted To: programming
Conversation: Identying all installed SQL Server instances on a machine
Subject: Identying all installed SQL Server instances on a machine
Hi,
I want to programmatically identify all SQL Server (2000 or 2005)
instances installed on a machine with Windows 2000 or 2003. One way is
to browse through the Windows registry and look for specific keys such
as HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server. But the
registry is organized differently for SQL 2005 than SQL 2000 and maybe
it will change again for the next SQL version. And things get messy when
both SQL 2000 & SQL
2005 instances co-exist on the same host. So is there an API I can use
to find the instances and not rely on Windows registry?
Thanks in advances for any pointers.
- VolcanoTony & ML:
Thanks a lot for the pointer.
- V
"Tony Sebion" <tony@.sebion.com> wrote in message
news:VlIkTDFmFHA.7716@.taurus.ad.nosellout.net...
I think I would use the SQL-DMO object to find SQL instances, then
filter that list to just the single computer you want to query.
Ref: http://www.sqlteam.com/item.asp?ItemID=5403
Good luck,
Tony Sebion
--Original Message--
From: Volcano [mailto:Volcano@.discussions.microsoft.com]
Posted At: Wednesday, August 03, 2005 11:55 AM
Posted To: programming
Conversation: Identying all installed SQL Server instances on a machine
Subject: Identying all installed SQL Server instances on a machine
Hi,
I want to programmatically identify all SQL Server (2000 or 2005)
instances installed on a machine with Windows 2000 or 2003. One way is
to browse through the Windows registry and look for specific keys such
as HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server. But the
registry is organized differently for SQL 2005 than SQL 2000 and maybe
it will change again for the next SQL version. And things get messy when
both SQL 2000 & SQL
2005 instances co-exist on the same host. So is there an API I can use
to find the instances and not rely on Windows registry?
Thanks in advance for any pointers.
- Volcano

Identying all installed SQL Server instances on a machine

Hi,
I want to programmatically identify all SQL Server (2000 or 2005) instances
installed on a machine with Windows 2000 or 2003. One way is to browse
through the Windows registry and look for specific keys such as
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Mi
crosoft SQL Server. But the registry
is organized differently for SQL 2005 than SQL 2000 and maybe it will change
again for the next SQL version. And things get messy when both SQL 2000 & SQ
L
2005 instances co-exist on the same host. So is there an API I can use to
find the instances and not rely on Windows registry?
Thanks in advances for any pointers.
- VolcanoSQL-DMO for SQL 2000 and SMO for SQL 2005.
ML

IDENTITY_INSERT

dear jeff johnson ,
thanks for ur response.
I have one table name fixtures in client machine .In that table one column
is identity type .now i am insert one Row from server database to that clien
t
database
now i have to on the identity_insert in client machine from server machine
give some suggestion.
sangeetha-server machine
sankar--client machine
i am running this query from my machine my machine name is sangeeta
EXEC master.dbo.xp_cmdshell 'osql -U scoremate -P scoremate -S sankar -Q
"set identity_insert scoremate.dbo.fixtures on "'
insert into openrowset('MSDASQL','DRIVER={SQL
Server};SERVER=sankar;UID=scoremate;PWD=
scoremate',
'select * from scoremate.dbo.fixtures')
select compcode,seasonid,matchid,matchdt,
time,round,roundtype,rounddesc,team1catg
,team1code,team2catg,team2code,
ground,umpires,genuser,
gendate,editdate,umpire1,thirdumpire,loc
ked,userid from
openrowset('MSDASQL','DRIVER={SQL
Server};SERVER=sankar;UID=scoremate;PWD=
scoremate',
'select compcode,seasonid,matchid=15,matchdt,
time,round,roundtype,rounddesc,team1catg
,team1code,team2catg,team2code,
ground,umpires,genuser,
gendate,editdate,umpire1,thirdumpire,loc
ked,userid from
scoremate.dbo.fixtures where matchid=13')Hi
Everything seems to point to the client machine?
You may be better off connecting to the server where you are doing the
inserts and not using your OPENROWSET as the destination of the insert.
John
"MOHAMED NASEER" wrote:

> dear jeff johnson ,
> thanks for ur response.
> I have one table name fixtures in client machine .In that table one colum
n
> is identity type .now i am insert one Row from server database to that cli
ent
> database
> now i have to on the identity_insert in client machine from server machine
> give some suggestion.
> sangeetha-server machine
> sankar--client machine
> i am running this query from my machine my machine name is sangeeta
> EXEC master.dbo.xp_cmdshell 'osql -U scoremate -P scoremate -S sankar -Q
> "set identity_insert scoremate.dbo.fixtures on "'
> insert into openrowset('MSDASQL','DRIVER={SQL
> Server};SERVER=sankar;UID=scoremate;PWD=
scoremate',
> 'select * from scoremate.dbo.fixtures')
> select compcode,seasonid,matchid,matchdt,
> time,round,roundtype,rounddesc,team1catg
,team1code,team2catg,team2code,
> ground,umpires,genuser,
> gendate,editdate,umpire1,thirdumpire,loc
ked,userid from
> openrowset('MSDASQL','DRIVER={SQL
> Server};SERVER=sankar;UID=scoremate;PWD=
scoremate',
> 'select compcode,seasonid,matchid=15,matchdt,
> time,round,roundtype,rounddesc,team1catg
,team1code,team2catg,team2code,
> ground,umpires,genuser,
> gendate,editdate,umpire1,thirdumpire,loc
ked,userid from
> scoremate.dbo.fixtures where matchid=13')sql