Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts

Thursday, March 22, 2012

Can't add DataSource or connect to database with Wizard

Hi,

I installed Visual Studio 2005 Beta 2 and could connect with it to my SQL 2000 Server. Now I installed on the same laptop SQL Server 2005, but the installation failed on some error. Now I uninstalled SQL Server 2005, but now I can't connect anymore to any datasource. The "Add new Data Source" is just not highlited and the Wizard from Tools Menu "Connect to Database" does not launch at all.

Any one has a solution?

thanks,
ImmanuelThe solution was to repair the Visual Studio 2005 installation.

Monday, March 19, 2012

can't (re)start SQLServerAgent after changing its logon credentials

Since Copy Databas Wizard failed to copy anything from remote SS20005 (both are with SP2 3054) in any combination,
I changed SQLServerAgent(myinstance_name) to run under Network from Local System with the help of SQL Server Configuration Manager

For this change it was restarted, failed to start again and continues to be stopped giving
"SQLServerAgent could not be started (reason: Unable to connect to server '<mymachine_name>\<myinstance_name>'; SQLServerAgent cannot start)."

I changed SQL Server Agent (myinstance_name) back to Local Service, then to Local System and still can't start it.

So, my questions:
1)
What has happened and how can I start SQLServerAgent?

2)
Why cannot I start it under Network Service? since it apparently should access remote resources for CDW to copy from remote SS2005

This is on MS Windows XP SP2

PS
After few trials I amnaged to restart it again under Local System but still cannot change to any different one

If you change the account under which SQL Agent starts you need to make sure that the account has permissions within SQL server or else each tim eit tries to access SQL Server it will fail. Have a look at these:

http://support.microsoft.com/kb/283811

http://support.microsoft.com/kb/907557

|||

You can verify the permissions, windows group membership required, etc for the service accounts in the following books online topic:

Setting Up Windows Service Accounts

http://msdn2.microsoft.com/en-us/library/ms143504.aspx

The NT Rights and Privleges section has the local windows group membership requirements - that one often gets overlooked for some reason. The help topic is pretty thorough and does a good job of covering the requirements.

Also note that as the article states, using Network Service isn't recommended. A domain account can provide the same network access but in a more secure manner. Otherwise you open some holes - network service means you give permissions needed for the CDW to the machine account. And then other apps, services running under network service get the permissions as well as they would be operating under the machine account.

-Sue

Saturday, February 25, 2012

Cannot specify 'dimension' for: Maintenance plan remove files older than

OS: Windows Server 2003 Standard Edition. MSDE 2000.

SQL Server Enterprise Manager Version 8.0.

The Maintenance Plan Wizard will not allow me to specify a value for the 'Remove Files...' I can enter a number but there is nothing in the drop down e.g. 3 'DAYS' perhaps?

Create then plan and then edit - yields the same result.

Any ideas on why there is no 'dimension' for Remove Files Older than ?

Appreciate any tips, ideas, etc.

Thank.s

Anybody have issues trying to specify a dimension for 'Remove Files...' either during Maintenance Wizard (create) or afterwards - edit properties?

The drop down - where you would expect a list of values like: day, week, month - is completely blank?

|||

I'm experiencing the exact same problem with my MSDE database. I cannot specify anything as to days, weeks, etc. It also will take other information, such as scheduling, directory, extension name, and actually create the jobs correctly, but then when you go back to the Maintenance Plan, you find the information has disappeared. If you try to modify any other aspect of the plan, you get an error, because this information is now missing. This is the only MSDE db I have, all the rest are standard or enterprise and work normally from the same Enterprise Manager.

I have not found any explanation or work-around for this problem.

Cannot specify 'dimension' for: Maintenance plan remove files older than

OS: Windows Server 2003 Standard Edition. MSDE 2000.

SQL Server Enterprise Manager Version 8.0.

The Maintenance Plan Wizard will not allow me to specify a value for the 'Remove Files...' I can enter a number but there is nothing in the drop down e.g. 3 'DAYS' perhaps?

Create then plan and then edit - yields the same result.

Any ideas on why there is no 'dimension' for Remove Files Older than ?

Appreciate any tips, ideas, etc.

Thank.s

Anybody have issues trying to specify a dimension for 'Remove Files...' either during Maintenance Wizard (create) or afterwards - edit properties?

The drop down - where you would expect a list of values like: day, week, month - is completely blank?

|||

I'm experiencing the exact same problem with my MSDE database. I cannot specify anything as to days, weeks, etc. It also will take other information, such as scheduling, directory, extension name, and actually create the jobs correctly, but then when you go back to the Maintenance Plan, you find the information has disappeared. If you try to modify any other aspect of the plan, you get an error, because this information is now missing. This is the only MSDE db I have, all the rest are standard or enterprise and work normally from the same Enterprise Manager.

I have not found any explanation or work-around for this problem.

Thursday, February 16, 2012

Cannot select Provider in Data Source Wizard Connection Manager

I think I either have an option set wrong or installed something wrong. When
I try to create a New Data Source in Data Model project, the dropdown box for
Provider is disabled and so SQLclient Data Provider is all I can do. I would
like to add a connection to an ODBC data source, which I should be able to
do. Any suggestions on what I can change to enable me to select the Provider?Semantic modelling in Model Designer supports native SQL provider only.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Shane_SDE" <ShaneSDE@.discussions.microsoft.com> wrote in message
news:054075DE-92DF-4127-9B53-0DB5FEB43670@.microsoft.com...
>I think I either have an option set wrong or installed something wrong.
>When
> I try to create a New Data Source in Data Model project, the dropdown box
> for
> Provider is disabled and so SQLclient Data Provider is all I can do. I
> would
> like to add a connection to an ODBC data source, which I should be able to
> do. Any suggestions on what I can change to enable me to select the
> Provider?

Tuesday, February 14, 2012

Cannot save my Maintenance plan

I use sa to login to sql 2005. I can save Maintenance plan using wizard, however, when I try to save maintenance plan using the maintenance plan design screen. I received error message "Apply to target server failed for job ...". When I check the job, there is no step in the job.

In the Maintenance wizard, there is no maintenance clean up task. I want to create a task to delete my backup file if it is older than certain days.

Any suggestions are welcome. Thanks in advance.

Hi

Dont use the wizard.

You can use the cleanup maintenacne task to cleanup backups files older than x days.

Cheers

|||

Only the wizard let me save my maintenance plan. I cannot save my maintenance plan if I use the design screen.

There is no Maintenance clean up task in the wizard.

|||

What error do you get when you save from designer ?

Gops Dwarak

|||

Oh I missed to see the error message in your mail.

This is the difference in behavior i noticed when created though wizard and through Designer

When you create maintenance plan with a name of job that is already existing through wizard , maintenance plan gets created successfully with a step added to the existing job. Expected behavior should have been to throw valid error saying "Job with this name already exists". When similar scenario is tried from Designer then error is thrown mentioning "Create failed for job 'job name' ". I have opened a bug to be fixed for next release.

Can you check whether job with plan name exists before creating the plan through designer ?

Also, this issue looks like more of SQL Server Agent issue. Can you look at the agent log file(through log viewer) when you try to perform this operation and see what message is logged in there. That may help to narrow down the issue

|||

I checked my sql server log and agent log. Both had no error message recorded.

I noticed if there is job name existed, the Designer thrown error 'Create failed for job...'. I manually deleted the job and maintenance and created from fresh. I got error message 'Apply to target server failed for job 'job name''. Acturally the maintenance plan is saved and job is saved. However, there is no job steps in the job.

I don't think it is SQL agent issue since I have run the job yet. The error occurred at the save process. I guess maybe a security issue. I am using sa to login and sa is dbo of msdb. I can use the wizard to save with no problem.

Thanks for any suggestions.

|||Any suggestions? Thanks.|||

Hi renching

I am afraid i canoot help you much more.

My experience with the new maintenance plans are that they suck.

When i try upgrade 2000 plans to 2005 they just give me errors, i hate the wizard it is nowhere near as user friendly as easy as in 2000.

Basically all i can advise is to do what i did, redo all plans from scratch in 2005.

But you say you have to use the wizard so i cannot help you there cos the wizard cant do what i want it to do, so i avoid it.

As far as exisitng jobs are concerned , i know i had to use sp_delete_maintenance_plan and sp_delete_maintenance_plan_job to properly clear out exisitng jobs and plans.\

Good luck.

Thanx

|||

Thanks. I wish the error message gave more information. Our application is built on SQL 2005. We have no conversions. All jobs are new. I got a lot problem with SQL 2005.

Thanks anyway. I hope someone will help me out here.

|||My SSIS is installed, however, it is disabled. Will this cause the problem?|||Try logging to SQL Server Management Studio on the local server as 'sa' with a server name of '.', then create, schedule, and save the new maintenence plan.|||

renching wrote:

My SSIS is installed, however, it is disabled. Will this cause the problem?

We shouldn't have a dependency on the SSIS service. Try installing SQL Server 2005 Service Pack 2.

http://www.microsoft.com/sql/sp2.mspx

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Cannot save my Maintenance plan

I use sa to login to sql 2005. I can save Maintenance plan using wizard, however, when I try to save maintenance plan using the maintenance plan design screen. I received error message "Apply to target server failed for job ...". When I check the job, there is no step in the job.

In the Maintenance wizard, there is no maintenance clean up task. I want to create a task to delete my backup file if it is older than certain days.

Any suggestions are welcome. Thanks in advance.

Hi

Dont use the wizard.

You can use the cleanup maintenacne task to cleanup backups files older than x days.

Cheers

|||

Only the wizard let me save my maintenance plan. I cannot save my maintenance plan if I use the design screen.

There is no Maintenance clean up task in the wizard.

|||

What error do you get when you save from designer ?

Gops Dwarak

|||

Oh I missed to see the error message in your mail.

This is the difference in behavior i noticed when created though wizard and through Designer

When you create maintenance plan with a name of job that is already existing through wizard , maintenance plan gets created successfully with a step added to the existing job. Expected behavior should have been to throw valid error saying "Job with this name already exists". When similar scenario is tried from Designer then error is thrown mentioning "Create failed for job 'job name' ". I have opened a bug to be fixed for next release.

Can you check whether job with plan name exists before creating the plan through designer ?

Also, this issue looks like more of SQL Server Agent issue. Can you look at the agent log file(through log viewer) when you try to perform this operation and see what message is logged in there. That may help to narrow down the issue

|||

I checked my sql server log and agent log. Both had no error message recorded.

I noticed if there is job name existed, the Designer thrown error 'Create failed for job...'. I manually deleted the job and maintenance and created from fresh. I got error message 'Apply to target server failed for job 'job name''. Acturally the maintenance plan is saved and job is saved. However, there is no job steps in the job.

I don't think it is SQL agent issue since I have run the job yet. The error occurred at the save process. I guess maybe a security issue. I am using sa to login and sa is dbo of msdb. I can use the wizard to save with no problem.

Thanks for any suggestions.

|||Any suggestions? Thanks.|||

Hi renching

I am afraid i canoot help you much more.

My experience with the new maintenance plans are that they suck.

When i try upgrade 2000 plans to 2005 they just give me errors, i hate the wizard it is nowhere near as user friendly as easy as in 2000.

Basically all i can advise is to do what i did, redo all plans from scratch in 2005.

But you say you have to use the wizard so i cannot help you there cos the wizard cant do what i want it to do, so i avoid it.

As far as exisitng jobs are concerned , i know i had to use sp_delete_maintenance_plan and sp_delete_maintenance_plan_job to properly clear out exisitng jobs and plans.\

Good luck.

Thanx

|||

Thanks. I wish the error message gave more information. Our application is built on SQL 2005. We have no conversions. All jobs are new. I got a lot problem with SQL 2005.

Thanks anyway. I hope someone will help me out here.

|||My SSIS is installed, however, it is disabled. Will this cause the problem?|||Try logging to SQL Server Management Studio on the local server as 'sa' with a server name of '.', then create, schedule, and save the new maintenence plan.|||

renching wrote:

My SSIS is installed, however, it is disabled. Will this cause the problem?

We shouldn't have a dependency on the SSIS service. Try installing SQL Server 2005 Service Pack 2.

http://www.microsoft.com/sql/sp2.mspx

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Cannot save maintenance plans

I am running SQL 2005 standard SP2 and I cannot save maintenance plans. Using the wizard I create the plan but it always fails with the following error messages:

An exception occurred while executing a Transact_SQL statement or batch

Invalid column name 'from_msx'.

Invalid column name 'has_targets'. (Microsoft SQL Server , Error: 207)

Invalid column name 'msx_job_id'. (Microsoft SQL Server, Error: 207)

Thanks

Todd

The column names you mention were added in SP2. This indicates that there is a mix of SP2 and earlier functionality involved in this problem.

Bring all elements up to SP2. If you have done so already, inspect installler logs to see if sp2 setup ran without error.

Good luck,

jkh

Cannot save Maintenance plan

I use sa to login to sql 2005. I can save Maintenance plan using wizard. However, when I try to save maintenance plan using the maintenance plan design screen, I received error message "Apply to target server failed for job ...". When I check the job, there is no step in the job.

In the Maintenance wizard, there is no maintenance clean up task. I want to create a task to delete my backup file if it is older than certain days.

Any suggestions are welcome. Thanks in advance.

have you considered using the script task?|||

Although Maintenance Plans are built on the SSIS infrastrcucture, they do have some aspects that we do not cover. Best to start in the SQL Server Tools forum. I'll move this thread for now.

Thanks

Donald