"unable to load MDT2G.DLL" (sql 7.0)?

I'm using sql server 7.0 - on "SQL Server Enterprise Manager" screen,
when I right click a table and select "Design Table" on the menu list,
I get error message box "Unable to load MDT2G.DLL".
I never had this before and don't know what happend.
What caused this and how to fix it ?
THANKS !
>
> I'm using sql server 7.0 - on "SQL Server Enterprise Manager"
> screen, when I right click a table and select "Design Table" on
> the menu list, I get error message box "Unable to load MDT2G.DLL".
> I never had this before and don't know what happened.
> What caused this and how to fix it ?
> THANKS !
>
The mdt2g.dll file could be corrupt. Try copying over it from your SQL CD
and see if it works for you.
Regards,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

"unable to load MDT2G.DLL" (sql 7.0)?

I'm using sql server 7.0 - on "SQL Server Enterprise Manager" screen,
when I right click a table and select "Design Table" on the menu list,
I get error message box "Unable to load MDT2G.DLL".
I never had this before and don't know what happend.
What caused this and how to fix it ?
THANKS !>
> I'm using sql server 7.0 - on "SQL Server Enterprise Manager"
> screen, when I right click a table and select "Design Table" on
> the menu list, I get error message box "Unable to load MDT2G.DLL".
> I never had this before and don't know what happened.
> What caused this and how to fix it ?
> THANKS !
>
--
The mdt2g.dll file could be corrupt. Try copying over it from your SQL CD
and see if it works for you.
Regards,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

"Too many requests being handled for user" error while accessing Report Manager

Hi,
When I try to access Report Manager(http://<reportserver>/Reports) I'm
getting the following error message:
"There are currently too many requests being handled for user:
[DOMAIN]\[USER]. Please wait until the current requests have finished
processing before issuing any more."
However there are no problems when I try to access the Report
Server(http://<reportserver>/ReportServer).
Has anyone encountered a similar situation before?
Thanks.
RamkiRestarting IIS resolves the issue. Increasing the
"MaxActiveReqForOneUser" in RSReportServer.config from its default of
20 might also be an option.
Ramki

"SQLServerAgent service hung on starting"

Since I installed sp4 for sql7 on 3 NT-machines last week, I get this message from Service Control Manager on every reboot of those PC's. After checking in the NT EventViewer, the SQLServerAgent service is really started but about 15-20 seconds after the error message.

EventID 7022
SERVICE CONTROL MANAGER
"SQLServerAgent service hung on starting"

Any idea how to solve this or what causes this?Take a look at your SQL Error log. SQL Server Agent will not be able to start unless the error log shows 'Recovery Complete'.|||Check your odbc administrator -> tracing -> check to see if it is enabled (if it is, stop the tracing).|||Thanks for your replies. Problem solved, the error message was caused because I also disabled the Messenger service (for security reasons). Now I enabled it again & the SQGAgent Service starts on reboot without the error warning. I still wonder why because I don't like leaving the Messenger service running.

"short circuit"/stop auto generating report after clicking report

In Report Manager, using a parameterless report or a report with parameters
that have default values, if one clicks on the report link in a folder, the
report automatically begins generating and then the data is viewable.
Is there any way to prevent the report from being (automatically) generated
so as to require the user to have to click the standard "View Report" button?
A solution might be in the "code"/RDL or perhaps the
"web.config"/RSWebApplication.config. Either is OK. Or anything else.On Jun 27, 1:28 pm, John <J...@.discussions.microsoft.com> wrote:
> In Report Manager, using a parameterless report or a report with parameters
> that have default values, if one clicks on the report link in a folder, the
> report automatically begins generating and then the data is viewable.
> Is there any way to prevent the report from being (automatically) generated
> so as to require the user to have to click the standard "View Report" button?
> A solution might be in the "code"/RDL or perhaps the
> "web.config"/RSWebApplication.config. Either is OK. Or anything else.
The easiest way to accomplish this is, in cases where report
parameters are used, to not have a default set for at least one of the
parameters. Sorry that I could not be of greater assistance.
Regards,
Enrique Martinez
Sr. Software Consultant

"Report Manager Virtual Directory" link greyed out in config. tool

I've just installed SQL Server 2005 Reporting Services on our development
servers and the "Report Manager Virtual Directory" link is disabled in the
configuration tool. Does anyone know why it is disabled, and how do I enable
it?
Also, the Web Service Identity link displays the following error message
when I click on it:
"There was an error while switching panels. The most likely cause is an
error retrieving WMI properties. The exception details are:
Object reference not set to an instance of an object."
I've verified that the "Windows Management Instrumentation" service is
running.
Background/current configuration:
- OS: Windows Server 2003 (Enterprise) SP1
- Web server separate from database server
- Reporting Svcs 2000 installed and working correctly
- Side-by-side installation of Reporting Svcs 2005 with 2000.
Any help would be greatly appreciated!
Thank you,
SanjayI am having the same issues on Server 2003 with SQL 2005.

"OutOfMemory" exception when listing subscriptions in "Report Manager"

Hi There,
We are having a problem in listing subscriptions in Report manager and
getting "OutOfMemory" exception.
Our Application has an event-based subscription management system, and
every-time an event gets fired on the Application-side, it creates an
one-off subscription on the Reporting Services. So overtime the number of
Subscriptions created on the reporting services has grown, and a particular
report has about 8000+ subscriptions to date now.
So when we try to list the subscriptions (for the purpose of management of
subscriptions) in the RS "Report Manager",
for that particular report, System gives an OutOfMemory exception. I think
Report Manager Calls internally
"ListSubscriptions" method (as explained in 840709) and couldn't cope up
with.
And i looked at MSDN Knowledgebase Article:840709, and increased the
"MemoryLimit" setting in RSReportServer.config, but there was no use.
By the way our Server has 2GB of RAM and we use Custom Authentication on
Reporting Services.
Any Suggestions are appreciated.
Regards
Raj ChidipudiI suggest you remove a number of the subscriptions via SQl Server Enterprise
Manager - remove a number of the relevant entries for the report from the
Subscriptions table.
Not tried it myself so I would backup before trying!!
You could also create an rss script to run at the end of day to remove all
subscriptions for a report, somthing like:
Public Sub Main()
rs.Credentials = System.Net.CredentialCache.DefaultCredentials
Dim subs As Subscription() = rs.ListSubscriptions(report, "")
If Not subs Is Nothing OrElse subs.Length > 0 Then
For Each subscript As Subscription In subs
rs.DeleteSubscription(subscript.SubscriptionID)
Next
End If
End Sub
Run it using the rs util with:
rs -i scriptname.rss -s http://ServerName/reportserver
Alan
"Raj Chidipudi" wrote:
> Hi There,
> We are having a problem in listing subscriptions in Report manager and
> getting "OutOfMemory" exception.
> Our Application has an event-based subscription management system, and
> every-time an event gets fired on the Application-side, it creates an
> one-off subscription on the Reporting Services. So overtime the number of
> Subscriptions created on the reporting services has grown, and a particular
> report has about 8000+ subscriptions to date now.
> So when we try to list the subscriptions (for the purpose of management of
> subscriptions) in the RS "Report Manager",
> for that particular report, System gives an OutOfMemory exception. I think
> Report Manager Calls internally
> "ListSubscriptions" method (as explained in 840709) and couldn't cope up
> with.
> And i looked at MSDN Knowledgebase Article:840709, and increased the
> "MemoryLimit" setting in RSReportServer.config, but there was no use.
> By the way our Server has 2GB of RAM and we use Custom Authentication on
> Reporting Services.
> Any Suggestions are appreciated.
> Regards
> Raj Chidipudi
>
>|||I think rs.DeleteSubscription("") would be the best bet.
We don't want to really mess with Reporting Services Database directly.
Anyway thanks for the suggestion.
Thanks
Raj Chidipudi
"Alan Byrne" <AlanByrne@.discussions.microsoft.com> wrote in message
news:116EB34B-1BD4-4FDC-ADB8-18BE795D3F22@.microsoft.com...
> I suggest you remove a number of the subscriptions via SQl Server
Enterprise
> Manager - remove a number of the relevant entries for the report from the
> Subscriptions table.
> Not tried it myself so I would backup before trying!!
> You could also create an rss script to run at the end of day to remove all
> subscriptions for a report, somthing like:
> Public Sub Main()
> rs.Credentials = System.Net.CredentialCache.DefaultCredentials
> Dim subs As Subscription() = rs.ListSubscriptions(report, "")
> If Not subs Is Nothing OrElse subs.Length > 0 Then
> For Each subscript As Subscription In subs
> rs.DeleteSubscription(subscript.SubscriptionID)
> Next
> End If
> End Sub
> Run it using the rs util with:
> rs -i scriptname.rss -s http://ServerName/reportserver
> Alan
>
> "Raj Chidipudi" wrote:
> > Hi There,
> >
> > We are having a problem in listing subscriptions in Report manager and
> > getting "OutOfMemory" exception.
> >
> > Our Application has an event-based subscription management system, and
> > every-time an event gets fired on the Application-side, it creates an
> > one-off subscription on the Reporting Services. So overtime the number
of
> > Subscriptions created on the reporting services has grown, and a
particular
> > report has about 8000+ subscriptions to date now.
> >
> > So when we try to list the subscriptions (for the purpose of management
of
> > subscriptions) in the RS "Report Manager",
> > for that particular report, System gives an OutOfMemory exception. I
think
> > Report Manager Calls internally
> > "ListSubscriptions" method (as explained in 840709) and couldn't cope up
> > with.
> >
> > And i looked at MSDN Knowledgebase Article:840709, and increased the
> > "MemoryLimit" setting in RSReportServer.config, but there was no use.
> > By the way our Server has 2GB of RAM and we use Custom Authentication on
> > Reporting Services.
> >
> > Any Suggestions are appreciated.
> >
> > Regards
> > Raj Chidipudi
> >
> >
> >

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
Julie
Hi Julie
"Kaidi" wrote:

> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John
|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
|||Hi Julie
"Kaidi" wrote:

> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!

> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.

> :P
> Julie
>
John
|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!

> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:

> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, yo
u
will see a node for management under which is SQL Server Agent and then Jobs
.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should b
e
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenan
ce plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:

> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!

> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.

> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!

> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

"Orphaned" maintenance plan

Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> > Followup, for anyone who happens to hit this post on a usenet search.
> > (I hate finding my problem with no solution.
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> > Do *not* simply delete the job rows that are causing the problem from
> > the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> > taken me a couple of hours to track down all of the pieces/references
> > to the job in other tables. I'm just hoping to heck I got them all...I
> > went manually through all of the delete commands in the sp_delete_job
> > procedure, and praying that it worked!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie

"Login failed for user" error

Hi

I have installed sql server on my standalone PC.

I used "window and sql mix authentication" for the sql server in the enterprise manager set up.
when I try to use the sql server login name for the startup service account, I have this error. "No Mapping between names and security IDs ".
So Even though I use mix authentication, I am still using window login name.

Then I create the DSN file.

But when I run the ASP program, I have this error "login fail for user-("user name that I used for dsn file configuration").

I try to configure the dsn file set up with both authentications, windows and sql login names.

But I got the error again.

I am really lost here.
Please help me. thanks...What's your connection string?|||when I try to use the sql server login name for the startup service account, I have this error. "No Mapping between names and security IDs ".

You cannot use a sql server login for the service accounts, these need to be windows accounts (domain or local user, or system account). The mixed authentication only applies to logins to the server.

"key not valid for use in the specified state"

I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
valid for use in the specified state" on any page of the Report Manager that
I try to access.
I've tried deleting and recreating the keys with no success. The search that
I've done in the MS Site have all pointed me to EFS errors. Anybody have any
ideas where I should go next?
Thanks.
DerrickI had that problem 6 months ago. After opening a support call with MS
and after many attempts to fix it, in the end the only process that
worked was to completely erase all traces of RS from the system and then
do a fresh install. Below is a list of the steps to take (note
especially step 5 - this was the deciding factor for me on the reinstall
fixing the problem)
1. Backup your existing solution files, such as .sln, .rdl, .rds files.
2. If the machine is a domain controller, do not install Reporting
Service on it. Use another machine instead.
3. Run Setup.exe of the SQL Server 2000 Reporting Services to launch the
Setup window.
4. Click "Remove Microsoft SQL Server 2000 Reporting Service" button in
the Setup window.
5. From Explorer, navigate to x:\Documents and Settings\<service
account>\Application Data\Microsoft\Crypto\RSA\S-1-5-20 and delete all
files located in this folder.
6. Delete all Reporting services related files under this folder
"x:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services" if present
7. Delete all Reporting Services Virtual Directories (ReportServer and
Reports) from IIS Manager if present.
8. Delete all Reporting Services Databases (ReportServer and
ReportServerTempDB) from SQL Server Enterprise Manager if present.
9. Re-boot the machine and log on using an Administrators group account.
10. Reinstall SQL Server 2000 Reporting Service on the machine.
brian smith
Derrick Powell wrote:
> I upgraded to Windows 2003 SP1, and now I keep getting the message: "Key not
> valid for use in the specified state" on any page of the Report Manager that
> I try to access.
> I've tried deleting and recreating the keys with no success. The search that
> I've done in the MS Site have all pointed me to EFS errors. Anybody have any
> ideas where I should go next?
> Thanks.
> Derrick
>

"Jump to Report" where the report is a linked report.

I setup a folder called _Master in Report Manager and I deploy all reports to
this folder. I setup additional folders through Report Manager that are
related to specific job functions: Sales, Customer Service, Marketing, etc.
Whenever I create a linked report using the "Jump to Report" feature in the
navigation tab, the linked report automatically defaults to the _Master
folder. Since I limit access to _Master solely to administrators, this means
I cannot use the "Jump to Report" drill down.
Is there any way to make the "Jump to Report" feature search for the report
in the current folder? I tried making references like ../Sales/Report1, but
this hard-coded Sales as the end folder. For instance, is there a way to do
../CurrentFolder/Report1 to make certain people in the Sales folder remain in
the Sales folder?
Sincerely,
Jonathan BaysThere is global variable Globals!ReportFolder
(http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSCREATE/htm/rcr_creating_expressions_v1_7ilv.asp
)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jonathan Bays" <JonathanBays@.discussions.microsoft.com> wrote in message
news:87926BDB-037E-419D-A591-22FF75B2F8A8@.microsoft.com...
>I setup a folder called _Master in Report Manager and I deploy all reports
>to
> this folder. I setup additional folders through Report Manager that are
> related to specific job functions: Sales, Customer Service, Marketing,
> etc.
> Whenever I create a linked report using the "Jump to Report" feature in
> the
> navigation tab, the linked report automatically defaults to the _Master
> folder. Since I limit access to _Master solely to administrators, this
> means
> I cannot use the "Jump to Report" drill down.
> Is there any way to make the "Jump to Report" feature search for the
> report
> in the current folder? I tried making references like ../Sales/Report1,
> but
> this hard-coded Sales as the end folder. For instance, is there a way to
> do
> ../CurrentFolder/Report1 to make certain people in the Sales folder remain
> in
> the Sales folder?
> Sincerely,
> Jonathan Bays

"HTTP status 400: Bad Request" - Reporting Services 2005

Has anyone ran into this error yet while testing Report Manager?
"The request failed with HTTP status 400: Bad Request."
I can deploy and access reports directly, but I receive the above error when
hitting the http://localhost/Reports URL (i.e. ReportManager)
Also, I'm seeing DCOM errors in the NT event log whenever this happens. A
search in the registry find CLSID references to network components (Network
Connection Manager Class, Network Connection Manager Connection Enumerator
Class, LAN Connection Manager Class, etc). Any ideas? Is there a security
configuration that I'm missing?
Here's an example entry:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 11/8/2005
Time: 8:23:48 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: *SERVERNAME*
Description:
The application-specific permission settings do not grant Local Activation
permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.I have the same problem and it turns out that you need to change the IP
address of your default website to "(all Unassigned)", instead of
specifiying a specific IP address.
thuan wrote:
> Has anyone ran into this error yet while testing Report Manager?
> "The request failed with HTTP status 400: Bad Request."
> I can deploy and access reports directly, but I receive the above error when
> hitting the http://localhost/Reports URL (i.e. ReportManager)
> Also, I'm seeing DCOM errors in the NT event log whenever this happens. A
> search in the registry find CLSID references to network components (Network
> Connection Manager Class, Network Connection Manager Connection Enumerator
> Class, LAN Connection Manager Class, etc). Any ideas? Is there a security
> configuration that I'm missing?
> Here's an example entry:
> Event Type: Error
> Event Source: DCOM
> Event Category: None
> Event ID: 10016
> Date: 11/8/2005
> Time: 8:23:48 AM
> User: NT AUTHORITY\NETWORK SERVICE
> Computer: *SERVERNAME*
> Description:
> The application-specific permission settings do not grant Local Activation
> permission for the COM Server application with CLSID
> {BA126AD1-2166-11D1-B1D0-00805FC1270E}
> to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security
> permission can be modified using the Component Services administrative tool.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.

"Full-Text Indexing" is Grayed Out, Disabled

I want to enable "Full-Text Indexing" in my Microsoft SQL Server 2000
database, except when I go into the SQL Server Enterprise Manager and
click on the "Tools" drop down menu in the tool bar, the option
"Full-Text Indexing" is grayed out (aka greyed out).
I think I need to start a service named MSSEARCH; however, when I go
into Start -> Settings -> Control Panel -> Administrative Tools ->
Services, I do not see any service whose name is close to "MSSEARCH".
I also tried `sqlftwiz` (SQL Full-Text Wizard) with several options,
but the closest I got was an error message stating "Cannot get
full-text default path from registry."
I also installed SQL Server Service Pack 3.
When I execute stored procedure `sp_fulltext_database 'enable'`, I get
this error message:
"Server: Msg 7609, Level 17, State 2, Procedure sp_fulltext_database,
Line 46
Full-Text Search is not installed, or a full-text component cannot be
loaded"
Therefore, how do I get the "Full-Text Indexing" to no longer be
grayed out?
Or, how to I install, start or implement full-text indexing?
Sounds like SQL FTS has not been installed.
Put your SQL Server cd on the cd platter.
double click setup.bat from the cd. click next.
select local computer, click next.
select upgrade, remove, or add components to an existing instance of SQL
Server, click next.
select the instance you wish to add SQL FTS to, click next.
select add components to your existing installation, click next.
In the component section give focus to Server Component (it should be given
focus by default).
In the sub components section, select full text search, click next. click
next, and accept all remaining defaults.
<charismatic_evangelist@.yahoo.com> wrote in message
news:dd8e1652.0409081147.21b78b87@.posting.google.c om...
> I want to enable "Full-Text Indexing" in my Microsoft SQL Server 2000
> database, except when I go into the SQL Server Enterprise Manager and
> click on the "Tools" drop down menu in the tool bar, the option
> "Full-Text Indexing" is grayed out (aka greyed out).
> I think I need to start a service named MSSEARCH; however, when I go
> into Start -> Settings -> Control Panel -> Administrative Tools ->
> Services, I do not see any service whose name is close to "MSSEARCH".
> I also tried `sqlftwiz` (SQL Full-Text Wizard) with several options,
> but the closest I got was an error message stating "Cannot get
> full-text default path from registry."
> I also installed SQL Server Service Pack 3.
> When I execute stored procedure `sp_fulltext_database 'enable'`, I get
> this error message:
> "Server: Msg 7609, Level 17, State 2, Procedure sp_fulltext_database,
> Line 46
> Full-Text Search is not installed, or a full-text component cannot be
> loaded"
> Therefore, how do I get the "Full-Text Indexing" to no longer be
> grayed out?
> Or, how to I install, start or implement full-text indexing?
|||C_E,
It is always a good idea to know what SQL Server version as well as Edition
is as the Full-Text Search (FTS) components are not supported on all SQL
Server 2000 Editions. See SQL Server 2000 Books Online (BOL) title "Features
Supported by the Editions of SQL Server 2000" as the "Microsoft Search
(MSSearch.exe) service is installed only with certain SQL Server editions.
Could you post the full output of the following SQL script?
select @.@.version
Installing SQL Server Service Pack 3 alone will not resolve this issue as
you will need to install the FTS components (if supported) and then
re-install SQL Server Service Pack 3 to fix any FTS bugs, issues, etc.
Depending upon the output of the sql script, you may be able to install the
FTS components from your SQL 2000 installation CD via custom installation
and select Full-Text Search under the server components list.
Regards,
John
<charismatic_evangelist@.yahoo.com> wrote in message
news:dd8e1652.0409081147.21b78b87@.posting.google.c om...
> I want to enable "Full-Text Indexing" in my Microsoft SQL Server 2000
> database, except when I go into the SQL Server Enterprise Manager and
> click on the "Tools" drop down menu in the tool bar, the option
> "Full-Text Indexing" is grayed out (aka greyed out).
> I think I need to start a service named MSSEARCH; however, when I go
> into Start -> Settings -> Control Panel -> Administrative Tools ->
> Services, I do not see any service whose name is close to "MSSEARCH".
> I also tried `sqlftwiz` (SQL Full-Text Wizard) with several options,
> but the closest I got was an error message stating "Cannot get
> full-text default path from registry."
> I also installed SQL Server Service Pack 3.
> When I execute stored procedure `sp_fulltext_database 'enable'`, I get
> this error message:
> "Server: Msg 7609, Level 17, State 2, Procedure sp_fulltext_database,
> Line 46
> Full-Text Search is not installed, or a full-text component cannot be
> loaded"
> Therefore, how do I get the "Full-Text Indexing" to no longer be
> grayed out?
> Or, how to I install, start or implement full-text indexing?
|||Given that I had the same problem as charismatic_evangelist@.yahoo.com, I
tried the steps that you gave below. The instance of the Server that I
applied it to was the (local)(Windows NT) server, where my database resides.
Even after going through all the steps, and having turned SQL FTS on, the
full text search is still greyed out when I right click on the particular
table I need to be able to search. Any other ideas of what to do?
- MacL
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukjtrBglEHA.2764@.TK2MSFTNGP11.phx.gbl...
> Sounds like SQL FTS has not been installed.
> Put your SQL Server cd on the cd platter.
> double click setup.bat from the cd. click next.
> select local computer, click next.
> select upgrade, remove, or add components to an existing instance of SQL
> Server, click next.
> select the instance you wish to add SQL FTS to, click next.
> select add components to your existing installation, click next.
> In the component section give focus to Server Component (it should be
> given
> focus by default).
> In the sub components section, select full text search, click next. click
> next, and accept all remaining defaults.
>
|||Mac,
While you may have the same *symptoms* as Charismatic_Evangelist, you may or
may not have the same problem, especially as s/he never provided his/her SQL
Server 2000 version & edition info. It is always a good idea to know what
SQL Server version as well as Edition is as the Full-Text Search (FTS)
components are not supported on all SQL Server 2000 Editions. See SQL Server
2000 Books Online (BOL) title "Features Supported by the Editions of SQL
Server 2000" as the "Microsoft Search (MSSearch.exe) service is installed
only with certain SQL Server editions. Could you post the full output of the
following SQL script?
select @.@.version
You should also review the following KB article Q270671 (Q270671) "PRB: Full
Text Search Menus Are Not Enabled for Local Windows NT Accounts" at
http://support.microsoft.com/default...;en-us;q270671 depending
upon how you have the MSSQLServer service startup account setup.
If you did recently upgrade or install the FTS components, could you also
attach the following SQL setup log files: sqlstp.log (usually located at
C:\WINNT\Temp) and SearchSetup.log usually located at C:\WINNT\. These files
can also help in troubleshooting FTS installation issues.
Regards,
John
"Mac Littlefield" <warrenlittlefield@.sbcglobal.net> wrote in message
news:#Ai13dnpEHA.3708@.TK2MSFTNGP10.phx.gbl...
> Given that I had the same problem as charismatic_evangelist@.yahoo.com, I
> tried the steps that you gave below. The instance of the Server that I
> applied it to was the (local)(Windows NT) server, where my database
resides.[vbcol=seagreen]
> Even after going through all the steps, and having turned SQL FTS on, the
> full text search is still greyed out when I right click on the particular
> table I need to be able to search. Any other ideas of what to do?
> - MacL
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukjtrBglEHA.2764@.TK2MSFTNGP11.phx.gbl...
click
>
|||There can be serveral causes of the Full-Text Index Table menu option not
being enabled
a.. SQL FTS is not enabled on this SQL server. Click here for instructions
on how to install SQL FTS on your SQL Server.
a.. You are not in the dbo role for this database
a.. The System Administrator role is not in the Local Administrators group
for this machine or the NTAuthority\Logon group is not in the System
Administrators group.
If you remove BUILTIN\Administrators and Full Text is enabled, add a login
account for the Local System account using sp_grantlogin [NT
Authority\System], and ensure that the login account is a member of the
sysadmin fixed server role. Here is some sample TSQL code to do this:
if not exists (select * from master.dbo.syslogins where loginname = N'NT
Authority\System')
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System', N'us_english'
GO
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
GO
a.. Something else yet undetermined. Microsoft acknowledges this problem in
this kb article
(http://support.microsoft.com/default...1&Product=sql2
k) and recommends that you use the full text stored procedures to manage
your catalog or tables.
When I run across this problem (I don't run across is often as typically I
use the full text stored procedures) I normally use the SQLFTSWiz.exe
program which can be found by default in: C:\Program Files\Microsoft SQL
Server\80\Tools\Binn you can launch it by opening a command prompt and
typing for NT Authentication:
sqlftwiz /n /sSQLServerName[\InstanceName] /dpubs
or for SQL Authentication:
sqlftwiz /sSQLServerName[\InstanceName] /dpubs /uAccount /pPassword
In both of the above examples, SQLServerName[\InstanceName] is the name of
the SQL Server you wish to connect to. If you are using the default instance
you would use the below:
sqlftwiz /sSQLServerName /dpubs /uAccount /pPassword
If you are using an instance, other than the default instance you would use
the below (where InstanceName is the name of the instance you are using):
sqlftwiz /sSQLServerName\InstanceName /dpubs /uAccount /pPassword
Pubs is the database you wish to create your full text table in.
The dialogs you get are for the most part identical to the dialogs you would
get if you were to just right click on a table. After the initial splash
screen select the table you wish to index. The rest of the dialogs are
identical to the dialogs you will see if you were to right click on a table
in EM and select Full Text Index table.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Mac Littlefield" <warrenlittlefield@.sbcglobal.net> wrote in message
news:%23Ai13dnpEHA.3708@.TK2MSFTNGP10.phx.gbl...
> Given that I had the same problem as charismatic_evangelist@.yahoo.com, I
> tried the steps that you gave below. The instance of the Server that I
> applied it to was the (local)(Windows NT) server, where my database
resides.[vbcol=seagreen]
> Even after going through all the steps, and having turned SQL FTS on, the
> full text search is still greyed out when I right click on the particular
> table I need to be able to search. Any other ideas of what to do?
> - MacL
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukjtrBglEHA.2764@.TK2MSFTNGP11.phx.gbl...
click
>

"Directory Listing Denied" Issue

Hi, I have a problem with viewing already deployed Report through Reports
Manager. I am able to see the list of reports in Reports Manager but when I
click on any report, I'm getting "Directory Listing Denied" error message.I
am using SQL Server Reporting Services 2000, on IIS6. Any ideas?Did you find a solution? One of our other administrators made some
configuration changes the other day and we are now experiencing the same
problem. I looked at the IIS settings and they appear to be the same that I
remember they always were. If I try to access the reports from
https://sitename/ReportServer, I am getting HTTP Error 403 - Forbidden.
I'm an admin on the box so I'm not sure why it would be forbidden.
"Chandrakumar" wrote:
> Hi, I have a problem with viewing already deployed Report through Reports
> Manager. I am able to see the list of reports in Reports Manager but when I
> click on any report, I'm getting "Directory Listing Denied" error message.I
> am using SQL Server Reporting Services 2000, on IIS6. Any ideas?
>

"Design Storage and Process the Cube" issue

To anyone who can help,
I am reviewing the processes in the Analysis Manager, and I am going
through the sample exercises offered by SQL Server's Analysis Manager Help.
So far, every step has been successful, but now I am running into a
problem. If you have the Analysis Manager installed, you should be able to
follow this directory to see the instructions I am following.
C:\Program Files\Microsoft Analysis
Services\Help80\Tutorial\design_stor_pro
c.htm
When I attempt to process the design storage to set the aggregations, it
is failing. I get the following error for why the process has failed:
[Microsoft][ODBC Driver Manager] Data source name not found and no d
efault
driver specified;IM002; Time:8/26/2004 5:25:00 PM
If you understand why this is happening, I would appreciate any tips. If I
go to redo the process it does show that I already have aggregates for the
cube. Does that mean it actually worked, or am I correct in my assumption
that the error is pointing to a problem that I need to resolve. Thanks for
any information!
CourtneyHi
Did u manage 2 fix the problem?
Udi
"Courtney Fay" wrote:

> To anyone who can help,
> I am reviewing the processes in the Analysis Manager, and I am going
> through the sample exercises offered by SQL Server's Analysis Manager Help
.
> So far, every step has been successful, but now I am running into a
> problem. If you have the Analysis Manager installed, you should be able t
o
> follow this directory to see the instructions I am following.
> C:\Program Files\Microsoft Analysis
> Services\Help80\Tutorial\design_stor_pro
c.htm
> When I attempt to process the design storage to set the aggregations,
it
> is failing. I get the following error for why the process has failed:
> [Microsoft][ODBC Driver Manager] Data source name not found and no
default
> driver specified;IM002; Time:8/26/2004 5:25:00 PM
> If you understand why this is happening, I would appreciate any tips. If
I
> go to redo the process it does show that I already have aggregates for the
> cube. Does that mean it actually worked, or am I correct in my assumption
> that the error is pointing to a problem that I need to resolve. Thanks fo
r
> any information!
> Courtney
>
>

"Design Storage and Process the Cube" issue

To anyone who can help,
I am reviewing the processes in the Analysis Manager, and I am going
through the sample exercises offered by SQL Server's Analysis Manager Help.
So far, every step has been successful, but now I am running into a
problem. If you have the Analysis Manager installed, you should be able to
follow this directory to see the instructions I am following.
C:\Program Files\Microsoft Analysis
Services\Help80\Tutorial\design_stor_proc.htm
When I attempt to process the design storage to set the aggregations, it
is failing. I get the following error for why the process has failed:
[Microsoft][ODBC Driver Manager] Data source name not found and no default
driver specified;IM002; Time:8/26/2004 5:25:00 PM
If you understand why this is happening, I would appreciate any tips. If I
go to redo the process it does show that I already have aggregates for the
cube. Does that mean it actually worked, or am I correct in my assumption
that the error is pointing to a problem that I need to resolve. Thanks for
any information!
Courtney
Hi
Did u manage 2 fix the problem?
Udi
"Courtney Fay" wrote:

> To anyone who can help,
> I am reviewing the processes in the Analysis Manager, and I am going
> through the sample exercises offered by SQL Server's Analysis Manager Help.
> So far, every step has been successful, but now I am running into a
> problem. If you have the Analysis Manager installed, you should be able to
> follow this directory to see the instructions I am following.
> C:\Program Files\Microsoft Analysis
> Services\Help80\Tutorial\design_stor_proc.htm
> When I attempt to process the design storage to set the aggregations, it
> is failing. I get the following error for why the process has failed:
> [Microsoft][ODBC Driver Manager] Data source name not found and no default
> driver specified;IM002; Time:8/26/2004 5:25:00 PM
> If you understand why this is happening, I would appreciate any tips. If I
> go to redo the process it does show that I already have aggregates for the
> cube. Does that mean it actually worked, or am I correct in my assumption
> that the error is pointing to a problem that I need to resolve. Thanks for
> any information!
> Courtney
>
>

"Change Tracking" with "Update Index in Background" FREEZE ENTERPRISE

Hi,
When trying to set up "Change Tracking" with "Update Index in Background"
the Enterprise Manager console freezes.
Do I need to stop some Windows services to do that ?
Configuration :
SQL Server 2000 + SP3
Windows 2000 + SP3
Any help will be appreciated.
Thanks.
This should not happen at all. What happens if you configure change tracking
with update index in background using TSQL.
Here is an example of how you would do this for the authors table:
exec sp_fulltext_table 'authors', 'start_change_tracking'
GO
exec sp_fulltext_table 'authors', 'start_background_updateindex'
GO
It is possible that you are experiencing some locking during the intial
population if you have a high number of inserts/updates/and deletes running.
Also are you running profiler? Profiler will degrade performance even while
you have paused the trace.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"Jean-Marc PUGIN" <jmpugin@.mobileworkers.com> wrote in message
news:euMN3dD3EHA.2804@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When trying to set up "Change Tracking" with "Update Index in Background"
> the Enterprise Manager console freezes.
> Do I need to stop some Windows services to do that ?
> Configuration :
> SQL Server 2000 + SP3
> Windows 2000 + SP3
> Any help will be appreciated.
> Thanks.
>
|||Jean-Marc,
Most likely setting "Change Tracking" with "Update Index in Background" has
launched either an Incremental (if the table has a timestamp column) or a
Full Population in order to sync-up the MSSearch controlled FT Catalog with
the SQL Server 2000 table. Depending upon your server's resources this may
cause very high CPU-usage as well as with high memory and disk I/O to occur
during certain phases of the Incremental or Full Population and this will
have the affect of temporarily freezing the Enterprise Manager. Note, you
can use SQL Profiler or Perfmon or Task Mgr. to monitor the system usage.
Regards,
John
"Jean-Marc PUGIN" <jmpugin@.mobileworkers.com> wrote in message
news:euMN3dD3EHA.2804@.TK2MSFTNGP15.phx.gbl...
> Hi,
> When trying to set up "Change Tracking" with "Update Index in Background"
> the Enterprise Manager console freezes.
> Do I need to stop some Windows services to do that ?
> Configuration :
> SQL Server 2000 + SP3
> Windows 2000 + SP3
> Any help will be appreciated.
> Thanks.
>
|||John-
I have seen your name on quite a few posts and I believe you are helping
one of my colleagues on a FTS problem.
I thought I saw somewhere that you might have a list of Microsoft Full
Text Search replacements?
I am having a heck of a time finding something to replace the MS FTS in
SQL Server 2000. So far all I can find are web crawlers.
Could you give me some suggestions?
Thanks,
Dave
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||I'm sorry - hit submit by mistake.
I was actually going to offer some assistance on this question.
I did a small FTS build the other day, and I had the same problem. I
was using Query Analyzer, and it took 10 minutes for the second command
to complete execution (see previous posting).
If you do this in EM, expect the same behavior. It will appear to
freeze up for quite a while until it processes the commands.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Database Scripting Question

I just used Enterprise Manager to create a script of my database. My goal is
to take this script and run it on another server to create a copy of the
database. When I ran the script to re-create the database, I got numerous
errors because Enterprise Manager created the script in such a way that
database objects are not created in the correct order. For example, in the
script EM created, it attempts to create a stored procedure which references
a view that hasn't been created yet. Obviously, EM should have scripted the
view first and then the stored proc.
Is there anything I can do about this? Or, is there a tool I can purchase
that scripts objects in the correct order? My goal here is to script my
database and then execute the script and create a database that is a clone
of the original.
Thanks very much.
DBGhost from http://www.innovartis.co.uk/home.aspx claims to be able to
script out the db in the right order.
Andrew J. Kelly SQL MVP
"Amos J. Soma" <amos_j_soma@.yahoo.com> wrote in message
news:Hcmdnb5cILblc8bfRVn-sQ@.buckeye-express.com...
>I just used Enterprise Manager to create a script of my database. My goal
>is to take this script and run it on another server to create a copy of the
>database. When I ran the script to re-create the database, I got numerous
>errors because Enterprise Manager created the script in such a way that
>database objects are not created in the correct order. For example, in the
>script EM created, it attempts to create a stored procedure which
>references a view that hasn't been created yet. Obviously, EM should have
>scripted the view first and then the stored proc.
> Is there anything I can do about this? Or, is there a tool I can purchase
> that scripts objects in the correct order? My goal here is to script my
> database and then execute the script and create a database that is a clone
> of the original.
> Thanks very much.
>
|||It sounds like you depenency records are messed up.
Check this site out, the tools are nice will do what you need.
http://www.wingenious.com/sqltools/index.html
Hello Amos,

> I just used Enterprise Manager to create a script of my database. My
> goal is to take this script and run it on another server to create a
> copy of the database. When I ran the script to re-create the database,
> I got numerous errors because Enterprise Manager created the script in
> such a way that database objects are not created in the correct order.
> For example, in the script EM created, it attempts to create a stored
> procedure which references a view that hasn't been created yet.
> Obviously, EM should have scripted the view first and then the stored
> proc.
> Is there anything I can do about this? Or, is there a tool I can
> purchase that scripts objects in the correct order? My goal here is to
> script my database and then execute the script and create a database
> that is a clone of the original.
> Thanks very much.
>
|||Hello Andrew.
not quite - but almost. The scripter tool will script out the individual
objects and the build component will build a database (give it any name you
like) using these scripts and building it in the correct order and this all
can be recorded into a script to use which is the goal of this discussion.
"Andrew J. Kelly" wrote:

> DBGhost from http://www.innovartis.co.uk/home.aspx claims to be able to
> script out the db in the right order.
> --
> Andrew J. Kelly SQL MVP
>
> "Amos J. Soma" <amos_j_soma@.yahoo.com> wrote in message
> news:Hcmdnb5cILblc8bfRVn-sQ@.buckeye-express.com...
>
>