Tuesday, March 27, 2012
Can't check "Check existing data on creation" in relationship
When I added relationship to table, checked "Check existing data on
creation" and clicked "Save" in Enterprise Management tool, it has no error.
However, when I check tables again, the "Check existing data on creation"
option was unchecked.
Help me!It's the expected behaviour: the first time you create the
relationship, the existing data is verified (if "Check existing data on
creation" is checked) and subsequently all the new data is verified (if
"Enforce relationship for INSERTs and UPDATEs" is checked).
If you modify something in the relationship (for example: the
relationship's name or the cascade updates/deletes checkboxes), the
existing data does not need be verified again (that's why this checkbox
is unchecked when you look at it later).
Only if you modify the relationship in more semnificative ways (for
example: different columns), you should make sure that you click on
"Check existing data on creation" so the existing data will be verified
according to the new relationship.
Razvan
Can't back up Encryption Key
I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91
> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)
I have tried with passwords with different combination but none of them seem to help. Any ideas?
It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.
In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003
-Tudor
|||Hi quantum_csfb
Have you had any luck resolving this?
I am getting the same error.
I am running XP Pro SP2.
Thanks.
|||Gr8 :-)
Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine
Many Thx
|||Hi
I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.
Any other suggestions?
Can't back up Encryption Key
I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91
> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)
I have tried with passwords with different combination but none of them seem to help. Any ideas?
It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.
In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003
-Tudor
|||Hi quantum_csfb
Have you had any luck resolving this?
I am getting the same error.
I am running XP Pro SP2.
Thanks.
|||Gr8 :-)
Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine
Many Thx
|||Hi
I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.
Any other suggestions?
Can't back up Encryption Key
I am trying to backup Encryption Key for my reporting service. Configuration tool, prompts for a encryption key file location and a strong password. When I provide the same and click OK, I get the following error:
ReportServicesConfigUI.WMIProvider.WMIProviderException: An unknown error has occurred in the WMI Provider. Error Code 80070A91
> System.Runtime.InteropServices.COMException (0x80070A91): Password doesn't meet the requirements of the filter dll's (Exception from HRESULT: 0x80070A91)
End of inner exception stack trace
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.BackupEncryptionKey(Byte[]& encryptedBytes, String password)
I have tried with passwords with different combination but none of them seem to help. Any ideas?
It looks like your system has a password complexity filter installed. If you search on the error message, you will see a number of articles explaining how you can build and install one; I would check to see if that's the case first.
In the absence of a password filter, the RS WMI provider will use the local Windows password policy rules on Windows 2003
-Tudor
|||Hi quantum_csfb
Have you had any luck resolving this?
I am getting the same error.
I am running XP Pro SP2.
Thanks.
|||Gr8 :-)
Of course this was the thing.
Using a password that complied with the windows police in complexity worked fine
Many Thx
|||Hi
I am also having the same problem of encryption key backup with same error message. I checked the Windows password policy and am adhering to that but still the same problem persists.
Any other suggestions?
Monday, March 19, 2012
Cann't create Legacy (SQL 2000) Maintenance Plans
and the install of this new tool removed the old SQL Server 2000 Enterprise
Manager.
Since 99% of my installed server base is still SQL Server 2000, here’s my
question.
How am I supposed to manage my SQL Server 2000 instances with the SQL Server
2005 tools?
When I connect to a SQL Server 2000 instance, using SQL 2005 Management
Studio, I can see under Legacy -> Database Maintenance Plans, the existing
plans; however I cannot create any new Legacy Maintenance plans.
Kurt
It sounds bad but you should have thought of that before you upgraded then.
The documentation in 2005 clearly spells this out. If you need to change or
create new 2000 maintenance plans then you should have a machine with 2000
EM on it for that purpose. You must have chosen to upgrade your existing
instance instead of doing a side by side installation. There is no problem
running 2000 and 2005 on the same box and having both EM and SSMS running at
the same time. You can reinstall 2000 client tools but I am not sure if you
need to uninstall 2005 first or not. I would try it first and see.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"kmoskal@.newsgroups.nospam" <zork@.newsgroups.nospam> wrote in message
news:1FC128B9-88F0-42CA-8684-1445A06BA3B0@.microsoft.com...
>I recently installed the SQL Server 2005 Management Studio on my
>workstation
> and the install of this new tool removed the old SQL Server 2000
> Enterprise
> Manager.
> Since 99% of my installed server base is still SQL Server 2000, here’s my
> question.
> How am I supposed to manage my SQL Server 2000 instances with the SQL
> Server
> 2005 tools?
> When I connect to a SQL Server 2000 instance, using SQL 2005 Management
> Studio, I can see under Legacy -> Database Maintenance Plans, the existing
> plans; however I cannot create any new Legacy Maintenance plans.
>
>
>
> --
> Kurt
Sunday, February 19, 2012
Cannot show editor for this task in SQL 2005 Management Studio
Hi,
I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe
Cannot show editor for this task.
Additional information:
Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)
I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.
Thanks,
Steve
|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||hello I have got the same problem, but in spanish.
The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.
I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.
Error: (spanish)
No se puede mostrar el editor para esta tarea.
Información adicional:
El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.
Nombre del parámetro: Value (System.Windows.Forms)
|||Strangely on my side, the day after having this error, everything was ok.
Did not apply any new service pack or correction att all.
Carl
|||Solved same way, yesterday I created again one of the tasks, and today I can edit all them.
Summary: Solution, wait until tomorrow.
|||Hello everyone,
Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:
1. If no action is taken, on the day after the original expiration date, the "backup set will expire" option will be reset to a date that is 14 days from the current date and the task will be editable as usual.
2. If editing the task is required on the day it was set to expire, then one of the following two solutions can be used:
Solution A: The new task can be created in place of the existing task.
Solution B: The Backup Database task can be made editable by changing the “Backup set will expire” property in BIDS and importing the package back to the Maintenance Plan designer. Here are the steps to follow:
Edit your Maintenance Plan in the Server Business Intelligence Development Studio (BIDS)
· Find SQL Server Business Intelligence Development Studio on the Start menu under Microsoft SQL Server 2005.
· From the File menu, create a New Project of type “Integration Services Project”.
· To import your Maintenance Plan into your new project, in the Solution Explorer window, right click on the ‘SSIS Packages’ folder and choose the ‘Add Existing Package’ option.
· In the “Add Copy of Existing Package” dialog
o Set the Package Location to SQL Server
o Provide authentication for your server.
o In the Package Path field , click the browse button to display the packages on your server.
o Navigate to ‘SSIS Package’, then ‘Maintenance Plans’.
o Select your Maintenance Plan and click OK. You see the Maintenance Plan that you just imported under the ‘SSIS Packages’ folder.
· Right-Click the Backup Database Task and select Properties.
· In the list of properties, navigate to the “ExpireDate” option and change the date to be at least one day ahead of the current date.
· Save the Package.
· In the Solution Explorer window, click on the name of the package. In the Properties panel, locate the Full Path to the package’s .dtsx file. Select the path and copy it to the clipboard.
· Exit the Business Intelligence Development Studio.
Re-import the Edited Package
· In Management Studio, click the Connect button and choose “Integration Services…” and connect to your server.
· Under Stored Packages open “MSDB”.
· Right click on the “Maintenance Plans” folder and select “Import Package”.
o Select “File System”.
o In the Package Path text box, paste in the previously copied .dtsx file path.
o Click in the Package Name text box to set the name, and click OK.
· When prompted to overwrite the existing package, say “Yes”.
Given these updates, the Backup Database Task should be editable from the Maintenance Plan designer.
Sorry for the inconvenience.
-Sirish
Cannot show editor for this task in SQL 2005 Management Studio
Hi,
I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe
Cannot show editor for this task.
Additional information:
Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)
I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.
Thanks,
Steve
|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||hello I have got the same problem, but in spanish.
The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.
I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.
Error: (spanish)
No se puede mostrar el editor para esta tarea.
Información adicional:
El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.
Nombre del parámetro: Value (System.Windows.Forms)
|||Strangely on my side, the day after having this error, everything was ok.
Did not apply any new service pack or correction att all.
Carl
|||Solved same way, yesterday I created again one of the tasks, and today I can edit all them.
Summary: Solution, wait until tomorrow.
|||Hello everyone,
Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:
1. If no action is taken, on the day after the original expiration date, the "backup set will expire" option will be reset to a date that is 14 days from the current date and the task will be editable as usual.
2. If editing the task is required on the day it was set to expire, then one of the following two solutions can be used:
Solution A: The new task can be created in place of the existing task.
Solution B: The Backup Database task can be made editable by changing the “Backup set will expire” property in BIDS and importing the package back to the Maintenance Plan designer. Here are the steps to follow:
Edit your Maintenance Plan in the Server Business Intelligence Development Studio (BIDS)
· Find SQL Server Business Intelligence Development Studio on the Start menu under Microsoft SQL Server 2005.
· From the File menu, create a New Project of type “Integration Services Project”.
· To import your Maintenance Plan into your new project, in the Solution Explorer window, right click on the ‘SSIS Packages’ folder and choose the ‘Add Existing Package’ option.
· In the “Add Copy of Existing Package” dialog
o Set the Package Location to SQL Server
o Provide authentication for your server.
o In the Package Path field , click the browse button to display the packages on your server.
o Navigate to ‘SSIS Package’, then ‘Maintenance Plans’.
o Select your Maintenance Plan and click OK. You see the Maintenance Plan that you just imported under the ‘SSIS Packages’ folder.
· Right-Click the Backup Database Task and select Properties.
· In the list of properties, navigate to the “ExpireDate” option and change the date to be at least one day ahead of the current date.
· Save the Package.
· In the Solution Explorer window, click on the name of the package. In the Properties panel, locate the Full Path to the package’s .dtsx file. Select the path and copy it to the clipboard.
· Exit the Business Intelligence Development Studio.
Re-import the Edited Package
· In Management Studio, click the Connect button and choose “Integration Services…” and connect to your server.
· Under Stored Packages open “MSDB”.
· Right click on the “Maintenance Plans” folder and select “Import Package”.
o Select “File System”.
o In the Package Path text box, paste in the previously copied .dtsx file path.
o Click in the Package Name text box to set the name, and click OK.
· When prompted to overwrite the existing package, say “Yes”.
Given these updates, the Backup Database Task should be editable from the Maintenance Plan designer.
Sorry for the inconvenience.
-Sirish
Cannot show editor for this task in SQL 2005 Management Studio
Hi,
I have setup a db backup maintenance plan with the SQL 2005 Mgmt Studio tool. When I double-clicked the 'Back up Database Task' object I got the following error message. My SQL 2005 client has been patched with SQL 2005 SP2. Does someone know about this problem? Thanks - Joe
Cannot show editor for this task.
Additional information:
Value of '4/17/2007 12:00:00 AM' is not valid for Value'. Value should be between 'MinDate' and 'MaxDate'. Parameter name: Value(System.Windows.Forms)
I haven't heard of this one before. Please file a defect report for this issue at http://connect.microsoft.com/sqlserver. Issues reported on the Connect site go directly into our internal issue tracking system so we don't lose any information. Be sure to note whether the maintenance plan existed before your updated to SP2 or if the plan is new.
Thanks,
Steve
|||I'm getting this as well. Did you get an idea when this might be fixed.|||I'm getting this also. Did you get an idea when this might be fixed.|||hello I have got the same problem, but in spanish.
The mantenience plan was created before updating to SP2, and now I can't edit the BackUp task.
I tryed diferent MSSMS Clients with the same server, and it always fails, so I assume this is from the server.
Error: (spanish)
No se puede mostrar el editor para esta tarea.
Información adicional:
El valor de '02/05/2007 0:00:00' no es válido para 'Value'. 'Value' debería estar entre 'MinDate' y 'MaxDate'.
Nombre del parámetro: Value (System.Windows.Forms)
|||Strangely on my side, the day after having this error, everything was ok.
Did not apply any new service pack or correction att all.
Carl
|||Solved same way, yesterday I created again one of the tasks, and today I can edit all them.
Summary: Solution, wait until tomorrow.
|||Hello everyone,
Thanks for reporting this issue. The problem is that once the expiration date is reached, the UI cannot be displayed because the date value is earlier than what is allowed. While a solution is being worked out and will be available in a major release, a few work-arounds have been identified:
1. If no action is taken, on the day after the original expiration date, the "backup set will expire" option will be reset to a date that is 14 days from the current date and the task will be editable as usual.
2. If editing the task is required on the day it was set to expire, then one of the following two solutions can be used:
Solution A: The new task can be created in place of the existing task.
Solution B: The Backup Database task can be made editable by changing the “Backup set will expire” property in BIDS and importing the package back to the Maintenance Plan designer. Here are the steps to follow:
Edit your Maintenance Plan in the Server Business Intelligence Development Studio (BIDS)
· Find SQL Server Business Intelligence Development Studio on the Start menu under Microsoft SQL Server 2005.
· From the File menu, create a New Project of type “Integration Services Project”.
· To import your Maintenance Plan into your new project, in the Solution Explorer window, right click on the ‘SSIS Packages’ folder and choose the ‘Add Existing Package’ option.
· In the “Add Copy of Existing Package” dialog
o Set the Package Location to SQL Server
o Provide authentication for your server.
o In the Package Path field , click the browse button to display the packages on your server.
o Navigate to ‘SSIS Package’, then ‘Maintenance Plans’.
o Select your Maintenance Plan and click OK. You see the Maintenance Plan that you just imported under the ‘SSIS Packages’ folder.
· Right-Click the Backup Database Task and select Properties.
· In the list of properties, navigate to the “ExpireDate” option and change the date to be at least one day ahead of the current date.
· Save the Package.
· In the Solution Explorer window, click on the name of the package. In the Properties panel, locate the Full Path to the package’s .dtsx file. Select the path and copy it to the clipboard.
· Exit the Business Intelligence Development Studio.
Re-import the Edited Package
· In Management Studio, click the Connect button and choose “Integration Services…” and connect to your server.
· Under Stored Packages open “MSDB”.
· Right click on the “Maintenance Plans” folder and select “Import Package”.
o Select “File System”.
o In the Package Path text box, paste in the previously copied .dtsx file path.
o Click in the Package Name text box to set the name, and click OK.
· When prompted to overwrite the existing package, say “Yes”.
Given these updates, the Backup Database Task should be editable from the Maintenance Plan designer.
Sorry for the inconvenience.
-Sirish
|||You can select the backup mainplan in the designer and press F4 to open the properties of the maintenanceplan in the designer.In the properties you can change the expiry date, this allows you to open the plan again for edit.
Friday, February 10, 2012
cannot rename instance of analysis server.missing reg key
when i use the rename instance tool i get this error saying it cannot find the regestry key
hkey_local_Machine\wow6432Node\Microsoft\Microsoft Sql Server\90
When i look for this key, it doesnt exist. My installation went perfectly. what is going wrong
There are 2 versions of ASInstanceRename utility. Make sure you use one that is installed with 64bit version of Analysis Server.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
You should use 64 bit version of asinstancerename utility on 64 bit machine to rename 32bit instances. It is intended to be able to handle 32bit instances.
To get 64bit version of asinstancerename, uninstall 32bit version SQL Tools from your machine and install them back using 64ibt CD.
That should get you going.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.