September 29, 2017 at 2:18 pm
I started the wizard to create the Integration Services Catalog and entered a password that was too short for our Windows policy. Corrected that and now get an error indicating. "String or binary data would be truncated. Invalid object name 'sys.trusted_assemblies'. Anyone know what the issue is?
September 29, 2017 at 2:26 pm
lmarkum - Friday, September 29, 2017 2:18 PMI started the wizard to create the Integration Services Catalog and entered a password that was too short for our Windows policy. Corrected that and now get an error indicating. "String or binary data would be truncated. Invalid object name 'sys.trusted_assemblies'. Anyone know what the issue is?
Never seen that before. Was SSISDB created successfully, or are you getting that when you try to create it?
September 29, 2017 at 2:36 pm
SSISDB did not create successfully after that error. The error prevents the wizard from finishing. I next looked to see how long the password was. It was longer than I intended so I shortened it a bit. Tried again and the wizard finished. Still doesn't explain the error though.
September 29, 2017 at 4:11 pm
lmarkum - Friday, September 29, 2017 2:36 PMSSISDB did not create successfully after that error. The error prevents the wizard from finishing. I next looked to see how long the password was. It was longer than I intended so I shortened it a bit. Tried again and the wizard finished. Still doesn't explain the error though.
If you are using a downloaded version of SSMS, try using the version of SSMS that installs with your SQL Server version - SQL Server 2014.
Sue
November 30, 2017 at 11:27 pm
Sue_H - Friday, September 29, 2017 4:11 PMlmarkum - Friday, September 29, 2017 2:36 PMSSISDB did not create successfully after that error. The error prevents the wizard from finishing. I next looked to see how long the password was. It was longer than I intended so I shortened it a bit. Tried again and the wizard finished. Still doesn't explain the error though.If you are using a downloaded version of SSMS, try using the version of SSMS that installs with your SQL Server version - SQL Server 2014.
Sue
It worked like a charm and thanks for saving my day.
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply