cannot save storedproc after SP3

hi
we found a bug in EM. we are unable to save/export/transfer a DTS package to
another remote box. is there any workaround or hotfix available?
AlexAlex
See if this helps
http://www.sqldts.com/default.aspx?6,105,204,0,1
Regards
John|||How are you trying ?
File | Save As | SQL Server ?
File | Save As | Structured Storage File ?
Transferring DTS Packages
http://www.sqldts.com/default.aspx?6,105,204,0,1
--
--
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"alex" <ntnewsNO@.SPAM.hrz3.hrz.tu-darmstadt.de> wrote in message
news:OgI#tPoUDHA.1280@.tk2msftngp13.phx.gbl...
> hi
> we found a bug in EM. we are unable to save/export/transfer a DTS package
to
> another remote box. is there any workaround or hotfix available?
>
> Alex
>|||hi
> How are you trying ?
> File | Save As | SQL Server ?
> File | Save As | Structured Storage File ?
this are 3 "save as" options in SP3 and 4 "save as" options in SP2 and
prior.
the third in SP3 is "Visual Basic File". in SP2 there is another Option
"Save as DTS package file" (sorry - the options is gone - i don't know the
exact name). we need this DTS package option for transfer...
Alex

Cannot save server properties on Case Sensitive instances

Hi all,

I've filled this suspect bug to Connect:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=282812

The issue is: I'm unable to save any change to server properties if instance is set to Case Sensitive collation .

The process returns an error like (translated from Spanish, so not exact message):

"Error in metadata manager. Log file extension should be .LOG. Error in metadata manager. Error setting ConfigurationSettings\Log\File configuration property.".

As far as I've tested this happens with any property you're trying to set when in CS collation.

My bypass has been to edit msmdsrv.ini file directly with Notepad, reverting CollationName to case insensitive.

Then everything goes fine.

Details:

Tested with AS 2005 SP2 Collation: Latin1_General_CS_AI Happens both with SSMS and direct scripting (as expected)

Best regards,

Jordi Rambla

Solid Quality Mentors

wenn Collation Latin1_CS and soon is, you should change in msmdsrv.ini in

<Log>

<File>msmdsrv.log</File>... </Log> to <File>msmdsrv.LOG</File>

Cannot save server properties on Case Sensitive instances

Hi all,

I've filled this suspect bug to Connect:

https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=282812

The issue is: I'm unable to save any change to server properties if instance is set to Case Sensitive collation .

The process returns an error like (translated from Spanish, so not exact message):

"Error in metadata manager. Log file extension should be .LOG. Error in metadata manager. Error setting ConfigurationSettings\Log\File configuration property.".

As far as I've tested this happens with any property you're trying to set when in CS collation.

My bypass has been to edit msmdsrv.ini file directly with Notepad, reverting CollationName to case insensitive.

Then everything goes fine.

Details:

Tested with AS 2005 SP2 Collation: Latin1_General_CS_AI Happens both with SSMS and direct scripting (as expected)

Best regards,

Jordi Rambla

Solid Quality Mentors

wenn Collation Latin1_CS and soon is, you should change in msmdsrv.ini in

<Log>

<File>msmdsrv.log</File>... </Log> to <File>msmdsrv.LOG</File>