Hello,
we want a new browser window to open if we click on a report element with a
hyperlink-action. A second report should be displayed in the new browser
window at the same time. Is this possible?
Regards,
RalphIn the field you want to link, go to the action property. Select jump
to URL and enter an expression like the following:
="javascript:void(window.open('http://www.google.com','_blank'))"
Where the http://www.google.com is where you should put the link to
your report. If you have parameters, you will have to modify the query
string to include the parameters & their values (by programatically
concatenating them).
If you do a search through these forums for "javascript new window"
(without quotes) you should get many samples on how to accomplish some
of this.
Good Luck.
Regards,
Dan
Showing posts with label browser. Show all posts
Showing posts with label browser. Show all posts
Friday, March 23, 2012
Wednesday, March 21, 2012
RS2005 - Response Time
When running a report in VS, the report run fast but when running the same
report via the browser (<servername>\reportserver), the report runs slow.
How can I increase the response time in running the report via the browser?
Thank you.One thing to remember, in VS it caches the data (look in your directory and
you will see a .data file). So sometimes this can give you an erroneous idea
of the time required.
Also, if it is the first time that RS has run in awhile you will get a big
delay. So run any report to make sure RS is up and active and then run your
report you are concerned about.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:BB36DBF2-4F3C-4BF7-8850-6CCC9639FE7C@.microsoft.com...
> When running a report in VS, the report run fast but when running the same
> report via the browser (<servername>\reportserver), the report runs slow.
> How can I increase the response time in running the report via the
> browser?
> Thank you.|||Do you know what 'awhile' is? Is it possible to run a schedule report
just to keep RS 'alive'?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
> One thing to remember, in VS it caches the data (look in your
> directory and you will see a .data file). So sometimes this can give
> you an erroneous idea of the time required.
> Also, if it is the first time that RS has run in awhile you will get a
> big delay. So run any report to make sure RS is up and active and then
> run your report you are concerned about.
>|||I have a simple report I keep open on my desktop that autoexecutes every 5
minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
>>>>>>>>>>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Asher_N" <compguy666@.hotmail.com> wrote in message
news:Xns97009891877C1compguy666hotmailcom@.207.46.248.16...
> Do you know what 'awhile' is? Is it possible to run a schedule report
> just to keep RS 'alive'?
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
>> One thing to remember, in VS it caches the data (look in your
>> directory and you will see a .data file). So sometimes this can give
>> you an erroneous idea of the time required.
>> Also, if it is the first time that RS has run in awhile you will get a
>> big delay. So run any report to make sure RS is up and active and then
>> run your report you are concerned about.
>>
>|||"Bruce L-C [MVP]" <brucelc@.newsgroup.nospam> wrote in
news:#wuXBil3FHA.3292@.tk2msftngp13.phx.gbl:
> I have a simple report I keep open on my desktop that autoexecutes
> every 5 minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
> If you are running Windows 2003 server for your IIS reportserver, then
> this
> is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default
> 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is
> pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling
> tab
> there is a checkbox for recycling worker processes - it is currently
> set to
> 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to
> be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report
> doesn't get
> the delay, set up a schedule for either a dummy or adhoc report to
> fire off
> like at 6am so that the report component worker processes get loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed
> to load
> back up.
> =-Chris
>>>>>>>>>>
>
Thanks
report via the browser (<servername>\reportserver), the report runs slow.
How can I increase the response time in running the report via the browser?
Thank you.One thing to remember, in VS it caches the data (look in your directory and
you will see a .data file). So sometimes this can give you an erroneous idea
of the time required.
Also, if it is the first time that RS has run in awhile you will get a big
delay. So run any report to make sure RS is up and active and then run your
report you are concerned about.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Terry" <Terry@.discussions.microsoft.com> wrote in message
news:BB36DBF2-4F3C-4BF7-8850-6CCC9639FE7C@.microsoft.com...
> When running a report in VS, the report run fast but when running the same
> report via the browser (<servername>\reportserver), the report runs slow.
> How can I increase the response time in running the report via the
> browser?
> Thank you.|||Do you know what 'awhile' is? Is it possible to run a schedule report
just to keep RS 'alive'?
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
> One thing to remember, in VS it caches the data (look in your
> directory and you will see a .data file). So sometimes this can give
> you an erroneous idea of the time required.
> Also, if it is the first time that RS has run in awhile you will get a
> big delay. So run any report to make sure RS is up and active and then
> run your report you are concerned about.
>|||I have a simple report I keep open on my desktop that autoexecutes every 5
minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
If you are running Windows 2003 server for your IIS reportserver, then this
is a simple issue - I'll explain what happens:
The report service engine, once it is idle for more than the default 20
minutes, the worker process is shutdown.
This is controlled by IIS.
Open up the Internet Information Services (IIS) Manager
Expand the server node then the application pools.
On my IIS machine, I created an application pool dedicated to the
reportserver & reportmanager virtual webs.
But anyways, for the application pool that the reportserver is pointing to
if you left everything to their defaults will be the DefaultAppPool.
Right click the default app pool and select properties.
There are two things that are checked by default - On the recycling tab
there is a checkbox for recycling worker processes - it is currently set to
1740 minutes (29 hours). Leave it.
The other one is on the performance tab - which is the one you are
interested in changing...
See the "Idle Timeout" section and increase the number of minutes to be 8
hours a typical working day - 8*60 = 480 minutes.
Next, to be sure the "morning person" that runs the first report doesn't get
the delay, set up a schedule for either a dummy or adhoc report to fire off
like at 6am so that the report component worker processes get loaded.
I hope this helps you.
There is no need to have a report fire off every minute to keep things
alive - it is just that the report service was "unloaded" and needed to load
back up.
=-Chris
>>>>>>>>>>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Asher_N" <compguy666@.hotmail.com> wrote in message
news:Xns97009891877C1compguy666hotmailcom@.207.46.248.16...
> Do you know what 'awhile' is? Is it possible to run a schedule report
> just to keep RS 'alive'?
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in
> news:uRucKBj3FHA.3708@.TK2MSFTNGP10.phx.gbl:
>> One thing to remember, in VS it caches the data (look in your
>> directory and you will see a .data file). So sometimes this can give
>> you an erroneous idea of the time required.
>> Also, if it is the first time that RS has run in awhile you will get a
>> big delay. So run any report to make sure RS is up and active and then
>> run your report you are concerned about.
>>
>|||"Bruce L-C [MVP]" <brucelc@.newsgroup.nospam> wrote in
news:#wuXBil3FHA.3292@.tk2msftngp13.phx.gbl:
> I have a simple report I keep open on my desktop that autoexecutes
> every 5 minutes. You could also try Chris' suggestion posted below:
>>>>>>>>>>
> If you are running Windows 2003 server for your IIS reportserver, then
> this
> is a simple issue - I'll explain what happens:
> The report service engine, once it is idle for more than the default
> 20
> minutes, the worker process is shutdown.
> This is controlled by IIS.
> Open up the Internet Information Services (IIS) Manager
> Expand the server node then the application pools.
> On my IIS machine, I created an application pool dedicated to the
> reportserver & reportmanager virtual webs.
> But anyways, for the application pool that the reportserver is
> pointing to
> if you left everything to their defaults will be the DefaultAppPool.
> Right click the default app pool and select properties.
> There are two things that are checked by default - On the recycling
> tab
> there is a checkbox for recycling worker processes - it is currently
> set to
> 1740 minutes (29 hours). Leave it.
> The other one is on the performance tab - which is the one you are
> interested in changing...
> See the "Idle Timeout" section and increase the number of minutes to
> be 8
> hours a typical working day - 8*60 = 480 minutes.
> Next, to be sure the "morning person" that runs the first report
> doesn't get
> the delay, set up a schedule for either a dummy or adhoc report to
> fire off
> like at 6am so that the report component worker processes get loaded.
> I hope this helps you.
> There is no need to have a report fire off every minute to keep things
> alive - it is just that the report service was "unloaded" and needed
> to load
> back up.
> =-Chris
>>>>>>>>>>
>
Thanks
Friday, March 9, 2012
RS question
Hi
i am new to Reporting Services,i have aquestion regarding Reporting Services.When i saw the Reporting Server in browser it was like version 9.0.So i want to whether RS2000 or RS2005 are installed on my machine.
Thank's a lot.
Hi,
8.x is 2k based, 9.x is 2k5 based.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
RS on clustered server
I installed clustered sql2k5 with RS, and went through RS configuration without error. But got following errors when try to browser RS site, IIS is running:
For reports site, I got:
Server Error in '/Reports' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: Could not load type 'Microsoft.ReportingServices.UI.GlobalApp'.
Source Error:
|
Source File: D:\MSSQL.3\Reporting Services\ReportManager\global.asax Line: 1
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
For reportserver site, I got:
Server Error in '/ReportServer' Application.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: The format of the file 'ReportingServicesWebServer' is invalid.
Source Error:
|
Source File: D:\MSSQL.3\Reporting Services\ReportServer\web.config Line: 30
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded.
|
Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300
Any idea? Thanks.
The error message states that the RS virtual roots (/reports, /reportserver) are mapped to ASP.NET 1.1.
RS 2005 will only work with ASP.NET 2.0. You could try to delete the virtual roots and recreate them through the RS configuration tool, or you could try to manually change the mappings to use ASP.NET 2.0 directly in IISAdmin.
-- Robert
|||Tried that but didn't work. In fact, I reinstalled reporting service last week and it fixed the problem. Thanks.Wednesday, March 7, 2012
RS install problem
When I try to browse th e reports directory from the IIS MAnager It bring up
a new
browser window with the message
" Unable to find
library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing the
file manually ,or reinstall by running aspnet_regiis -c"
I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
anything.Asp.NET Framework1.1 is alreaddy installed in the server.
Does anybody have any indeas.Any suggestions is greatly appreciated.Did you let RS install as the default website? If not, then that is your
problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> When I try to browse th e reports directory from the IIS MAnager It bring
> up
> a new
> browser window with the message
> " Unable to find
> library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> the
> file manually ,or reinstall by running aspnet_regiis -c"
> I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> Does anybody have any indeas.Any suggestions is greatly appreciated.
>|||Thanks for replying bruce.
The tool took the Virtual Directory name "Reports" and "ReportServer" under
the default website of IIS.
Should I install it in a seperate website other than the default website'
Ranjan Mitra
FORD Motor co.
"Bruce L-C [MVP]" wrote:
> Did you let RS install as the default website? If not, then that is your
> problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
> news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> > When I try to browse th e reports directory from the IIS MAnager It bring
> > up
> > a new
> > browser window with the message
> > " Unable to find
> > library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> > the
> > file manually ,or reinstall by running aspnet_regiis -c"
> >
> > I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> > anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> >
> > Does anybody have any indeas.Any suggestions is greatly appreciated.
> >
>
>
a new
browser window with the message
" Unable to find
library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing the
file manually ,or reinstall by running aspnet_regiis -c"
I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
anything.Asp.NET Framework1.1 is alreaddy installed in the server.
Does anybody have any indeas.Any suggestions is greatly appreciated.Did you let RS install as the default website? If not, then that is your
problem.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> When I try to browse th e reports directory from the IIS MAnager It bring
> up
> a new
> browser window with the message
> " Unable to find
> library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> the
> file manually ,or reinstall by running aspnet_regiis -c"
> I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> Does anybody have any indeas.Any suggestions is greatly appreciated.
>|||Thanks for replying bruce.
The tool took the Virtual Directory name "Reports" and "ReportServer" under
the default website of IIS.
Should I install it in a seperate website other than the default website'
Ranjan Mitra
FORD Motor co.
"Bruce L-C [MVP]" wrote:
> Did you let RS install as the default website? If not, then that is your
> problem.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "RanjanFord" <RanjanFord@.discussions.microsoft.com> wrote in message
> news:002D0510-DE6B-4F3E-B1AA-B12E44A42C52@.microsoft.com...
> > When I try to browse th e reports directory from the IIS MAnager It bring
> > up
> > a new
> > browser window with the message
> > " Unable to find
> > library'/aspnet_clien/system_web/1_1_4322/WebUIValidation.js'.Try placing
> > the
> > file manually ,or reinstall by running aspnet_regiis -c"
> >
> > I followed the instructions & ran aspnet_regiis.exe ,but it did'nt help
> > anything.Asp.NET Framework1.1 is alreaddy installed in the server.
> >
> > Does anybody have any indeas.Any suggestions is greatly appreciated.
> >
>
>
Tuesday, February 21, 2012
RS 2005: Excessively Long String error when printing
I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:
Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?
Jon,
We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.
I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.
Is there any work around to this issue?
|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.
The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.
|||Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.
-Dan
|||Sure
SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.
|||Thanks so much Brad - really appreciate the help.
Jon
|||Brad -
In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?
Thanks,
Jon
|||I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.
Thanks
-Dan
Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.
Jon
|||It does indeed! Thanks for your note Jon!RS 2005: Excessively Long String error when printing
I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:
Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?
Jon,
We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.
I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.
Is there any work around to this issue?
|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.
The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.
|||Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.
-Dan
|||Sure
SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.
|||Thanks so much Brad - really appreciate the help.
Jon
|||Brad -
In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?
Thanks,
Jon
|||I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.
Thanks
-Dan
Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.
Jon
|||It does indeed! Thanks for your note Jon!RS 2005: Excessively Long String error when printing
I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:
Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?
Jon,
We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.
I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.
Is there any work around to this issue?
|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.
The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.
|||Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.
-Dan
|||Sure
SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.
|||Thanks so much Brad - really appreciate the help.
Jon
|||Brad -
In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?
Thanks,
Jon
|||I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.
Thanks
-Dan
Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.
Jon
|||It does indeed! Thanks for your note Jon!
Subscribe to:
Posts (Atom)