Anyone Else getting these errors?

[Jon Fincher (MS)]

"Brian Oblivious" <bria...@hotmail.com> wrote in
news:088e01c2d127$e1fc8e30$d7f82ecf@TK2MSFTNGXA14:

> Hello All,
>
> Anyone else getting any types of errors when attempting to
> open an existing .SLX file? I am getting two different
> errors, and sometimes they show up in the same day of
> development (so no backups made and the SLX with all work
> is toast!). I found one other reference to one of the two
> errors I am getting: "An error occurred while opening
> file: "C:\foo\bar.slx Code = 0x80070057 Description = The
> parameter is incorrect." (the one shown in attached
> screenshot). When I get the other error again, I'll post
> here as well. I am generally just making the same types
> of changes, etc. in the TA and the SLX saves just fine,
> etc. but occasionally, when attempting to open one (about
> six times last week, on six different revisions of the
> SLX) I get this error and the other one.

Just a wild stab in the dark here - do these SLX's have MUI components in
them?

--
--Jon, MS

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Hakan]

I remember making an SLX file corrupt by shutting
down SQL server while Target Designer was running.

>-----Original Message-----
>Hello All,
>
>Anyone else getting any types of errors when attempting to
>open an existing .SLX file? I am getting two different
>errors, and sometimes they show up in the same day of
>development (so no backups made and the SLX with all work
>is toast!). I found one other reference to one of the two
>errors I am getting: "An error occurred while opening
>file: "C:\foo\bar.slx Code = 0x80070057 Description = The
>parameter is incorrect." (the one shown in attached
>screenshot). When I get the other error again, I'll post
>here as well. I am generally just making the same types
>of changes, etc. in the TA and the SLX saves just fine,
>etc. but occasionally, when attempting to open one (about
>six times last week, on six different revisions of the
>SLX) I get this error and the other one.
>

>Any ideas?
>
>

[Brian Oblivious]

Hello Jon,

Thanks for the reply, but unfortunately, no the SLXs in
question do not contain MUI components. These errors have
occurred at various stages in refining my builds, but the
target application I am working with doesn't require MUI
functionality so that's probably not the issue here.

Thanks again.

>.
>

[Brian Oblivious]

Hello, and thanks for the reply.

I don't make a habit of shutting down the sql server at
any point during my development processes, so I'd have to
rule this out.

Thanks for the insight though!

>.
>

[Heidi Linda]

Just a thought - I used to get the occasional corrupt SLX
when the machine ran out of memory.
What else are you doing at the time, and how much memory
do you have?
Accidentally starting a second copy of TD is a sure way to
muff your .slx

[Jon Fincher (MS)]

"Brian Oblivious" <bria...@hotmail.com> wrote in

news:06fd01c2d201$e087ed80$2f01...@phx.gbl:

>
> Hello, and thanks for the reply.
>
> I don't make a habit of shutting down the sql server at
> any point during my development processes, so I'd have to
> rule this out.
>
> Thanks for the insight though!
>
>>-----Original Message-----
>>I remember making an SLX file corrupt by shutting
>>down SQL server while Target Designer was running.

Important safety tips - thanks. :-)

OK, one other thing to look at - what's the size of the runtime being
generated? Or at least, what's the size that the size estimation feature
is reporting?