Error running report: business

Showing posts with label business. Show all posts

Friday, March 23, 2012

Error when limiting memory usage with OSQL.EXE

When trying to limit the memory usage of the SQL components of Small
Business Server, I get an error message I don't know what to do with.
I searched for an osql internal command reference, but all the references I
found are about specific problems.
Here is my input and the result:
osql -E -S sbs01\sbsmonitoring
1> sp_configure 'show advanced options',1
2> reconfigure with override
3> go
Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement to install.
I intended to follow that with the following commands, but didn't get that
far:
sp_configure 'max server memory', 70
reconfigure with override
go
--
Reply in group, but if emailing add another
zero, and remove the last word.I think you need to remove the first go or just run
> sp_configure 'max server memory', 70
> reconfigure with override
--
Jason Massie
www: http://statisticsio.com
rss: http://statisticsio.com/Home/tabid/36/rssid/1/Default.aspx
"Tom Del Rosso" <td_01@.att.net.invalid> wrote in message
news:eqyFxBhLIHA.3832@.TK2MSFTNGP04.phx.gbl...
> When trying to limit the memory usage of the SQL components of Small
> Business Server, I get an error message I don't know what to do with.
> I searched for an osql internal command reference, but all the references
> I
> found are about specific problems.
>
> Here is my input and the result:
> osql -E -S sbs01\sbsmonitoring
> 1> sp_configure 'show advanced options',1
> 2> reconfigure with override
> 3> go
> Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.
>
> I intended to follow that with the following commands, but didn't get that
> far:
> sp_configure 'max server memory', 70
> reconfigure with override
> go
>
> --
> Reply in group, but if emailing add another
> zero, and remove the last word.
>|||Your advanced options are already set to 1 (enabled).
Now run the second set and you should be fine.
I don't see an error. I would also recommend using 100 instead of 70.
--
Claus
"Tom Del Rosso" <td_01@.att.net.invalid> wrote in message
news:eqyFxBhLIHA.3832@.TK2MSFTNGP04.phx.gbl...
> When trying to limit the memory usage of the SQL components of Small
> Business Server, I get an error message I don't know what to do with.
> I searched for an osql internal command reference, but all the references
> I
> found are about specific problems.
>
> Here is my input and the result:
> osql -E -S sbs01\sbsmonitoring
> 1> sp_configure 'show advanced options',1
> 2> reconfigure with override
> 3> go
> Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.
>
> I intended to follow that with the following commands, but didn't get that
> far:
> sp_configure 'max server memory', 70
> reconfigure with override
> go
>
> --
> Reply in group, but if emailing add another
> zero, and remove the last word.
>|||Hi Tom
What error message are you getting?
(If you're referring to this:
> Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.
please note that is not an error. It is the normal response to any
sp_configure command to set a value. SQL Server doesn't check to see if the
next statement is the RECONFIGURE before generating this message.)
If that was the response, you were ready to go on, but it's probably a good
thing you didn't. Setting memory to only 70MB is not a good idea. Although
technically SQL Server might be able to run with this little, you probably
won't be able to get any work done at all.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Tom Del Rosso" <td_01@.att.net.invalid> wrote in message
news:eqyFxBhLIHA.3832@.TK2MSFTNGP04.phx.gbl...
> When trying to limit the memory usage of the SQL components of Small
> Business Server, I get an error message I don't know what to do with.
> I searched for an osql internal command reference, but all the references
> I
> found are about specific problems.
>
> Here is my input and the result:
> osql -E -S sbs01\sbsmonitoring
> 1> sp_configure 'show advanced options',1
> 2> reconfigure with override
> 3> go
> Configuration option 'show advanced options' changed from 1 to 1. Run the
> RECONFIGURE statement to install.
>
> I intended to follow that with the following commands, but didn't get that
> far:
> sp_configure 'max server memory', 70
> reconfigure with override
> go
>
> --
> Reply in group, but if emailing add another
> zero, and remove the last word.
>|||"Kalen Delaney" <replies@.public_newsgroups.com> wrote in message
news:uS6ahRhLIHA.2024@.TK2MSFTNGP05.phx.gbl
> Hi Tom
> What error message are you getting?
> (If you're referring to this:
>> Configuration option 'show advanced options' changed from 1 to 1.
>> Run the RECONFIGURE statement to install.
> please note that is not an error. It is the normal response to any
> sp_configure command to set a value. SQL Server doesn't check to see
> if the next statement is the RECONFIGURE before generating this
> message.)
> If that was the response, you were ready to go on, but it's probably
> a good thing you didn't. Setting memory to only 70MB is not a good
> idea. Although technically SQL Server might be able to run with this
> little, you probably won't be able to get any work done at all.
Thanks all.
I should have mentioned that what I expected was "DBCC execution completed"
on the line following go. I thought that, without it, the command must have
failed.
I will use 100MB as Claus suggested. 70MB has worked with other SBS's and I
know I'm not the only SBS admin who has used that value, but I'll do as you
say.
Reply in group, but if emailing add another
zero, and remove the last word.sql

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Hi,
I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the SBS
2003 server Premium).
I installed the OS lately and made all the Microsoft update.
I am now trying to install the SQL 2000 server and get this error message:
(It is the english translation of what I get on my screen)
Error message: "A previous installation program created operation files
waiting for Installtion on your computer. You have to reboot it before
executing the installation."
Of course I rebooted my server, but nothing happened.
Any idea of what to do ?
Thank you for your helpDid you try installing again after the reboot? Was there an error code
listed?
From KB Article 257716:
Q. What should I do if the installation of SQL Server 2000 is unsuccessful?
A. If you have an unsuccessful installation, you can examine two files to
help determine what went wrong. The Sqlstp.log file, which is located in the
Windows directory, gives detailed information on what setup is doing and
contains all errors encountered during setup. Reviewing this file will give
you a better understanding of where setup fails and why.
During the configuration portion of setup, SQL Server setup runs an
application called Cnfgsvr.exe to configure the SQL Server. This application
starts SQL Server, connects to it, and then runs the initial installation
scripts. Any error encountered during this process is also written to the
Sqlstp.log file; however, you should also review the SQL Server error log,
named "Errorlog" with no file extension, located by default in the Program
Files\Microsoft SQL Server\Mssql\Log directory. This error log contains
errors that SQL Server encounters when setup attempts to start SQL Server,
which may provide further insight into the failure.
If you cannot determine the cause of the Setup failure, save the two files
just mentioned and call Microsoft Product Support Services (PSS) to speak to
a SQL Server Support Professional who will help you to resolve your problem.
Note that when the Setup application fails, it rolls back all changes to the
file system, which includes removing any copied files and changes that were
made to the registry.
HTH
Jerry
"Alambiki" <alambiki@.yahoo.com> wrote in message
news:dj5qnl$ok9$1@.reader1.imaginet.fr...
> Hi,
> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
> SBS
> 2003 server Premium).
> I installed the OS lately and made all the Microsoft update.
> I am now trying to install the SQL 2000 server and get this error message:
> (It is the english translation of what I get on my screen)
> Error message: "A previous installation program created operation files
> waiting for Installtion on your computer. You have to reboot it before
> executing the installation."
> Of course I rebooted my server, but nothing happened.
> Any idea of what to do ?
> Thank you for your help
>|||Yes I tried to reinstall after reboot.
I found the Sqlstp.log file, but am not able to understand it.
If someone has an idea...
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
> Did you try installing again after the reboot? Was there an error code
> listed?
> From KB Article 257716:
> Q. What should I do if the installation of SQL Server 2000 is
> unsuccessful?
> A. If you have an unsuccessful installation, you can examine two files to
> help determine what went wrong. The Sqlstp.log file, which is located in
> the Windows directory, gives detailed information on what setup is doing
> and contains all errors encountered during setup. Reviewing this file will
> give you a better understanding of where setup fails and why.
> During the configuration portion of setup, SQL Server setup runs an
> application called Cnfgsvr.exe to configure the SQL Server. This
> application starts SQL Server, connects to it, and then runs the initial
> installation scripts. Any error encountered during this process is also
> written to the Sqlstp.log file; however, you should also review the SQL
> Server error log, named "Errorlog" with no file extension, located by
> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
> This error log contains errors that SQL Server encounters when setup
> attempts to start SQL Server, which may provide further insight into the
> failure.
> If you cannot determine the cause of the Setup failure, save the two files
> just mentioned and call Microsoft Product Support Services (PSS) to speak
> to a SQL Server Support Professional who will help you to resolve your
> problem. Note that when the Setup application fails, it rolls back all
> changes to the file system, which includes removing any copied files and
> changes that were made to the registry.
>
> HTH
> Jerry
> "Alambiki" <alambiki@.yahoo.com> wrote in message
> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>|||What were the last few successful entries? Do you have an installation that
WAS successful that you can compare it to?
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356ae9a$0$4336$626a54ce@.news.free.fr...
> Yes I tried to reinstall after reboot.
> I found the Sqlstp.log file, but am not able to understand it.
> If someone has an idea...
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files to
>> help determine what went wrong. The Sqlstp.log file, which is located in
>> the Windows directory, gives detailed information on what setup is doing
>> and contains all errors encountered during setup. Reviewing this file
>> will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS) to
>> speak to a SQL Server Support Professional who will help you to resolve
>> your problem. Note that when the Setup application fails, it rolls back
>> all changes to the file system, which includes removing any copied files
>> and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>|||I already installed SBS + SQL on this server. It is the second time I
install it on this server. The only thing that changes is that I updated
with the latest ms update + installed symantec lifestate...
here is the log of SQLstp.log
19:00:30 Begin Setup
19:00:30 8.00.194
19:00:30 Mode = Normal
19:00:30 ModeType = NORMAL
19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
19:00:30 ValueFTS returned: 1
19:00:30 ValuePID returned: 1
19:00:30 ValueLic returned: 1
19:00:30 System: Small Business Server
19:00:30 SQL Server ProductType: Standard Edition [0x2]
19:00:30 Begin Action: SetupInitialize
19:00:30 End Action SetupInitialize
19:00:30 Begin Action: SetupInstall
19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
...
19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
19:00:30 Windows Directory=C:\WINDOWS\
19:00:30 Program Files=C:\Program Files\
19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
19:00:30 Begin Action: SetupInstall
19:00:30 Begin Action: CheckFixedRequirements
19:00:30 Platform ID: 0xf000
19:00:30 Version: 5.2.3790
19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
19:00:31 End Action: CheckFixedRequirements
19:00:31 Begin Action: ShowDialogs
19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
19:00:31 Begin Action ShowDialogsHlpr: 0x1
19:00:31 Begin Action: DialogShowSdWelcome
19:00:32 End Action DialogShowSdWelcome
19:00:32 Dialog 0x1 returned: 1
19:00:32 End Action ShowDialogsHlpr
19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
19:00:32 Begin Action ShowDialogsHlpr: 0x2
19:00:32 Begin Action: DialogShowSdMachineName
19:01:07 ShowDlgMachine returned: -1
19:01:07 ShowDlgMachine: GetLastError returned: 0
19:01:07 Opération réussie.
19:01:07 End Action DialogShowSdMachineName
19:01:07 End Action ShowDialogs
19:01:07 Action CleanUpInstall:
19:01:07 StatsGenerate returned: 2
19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
19:01:07 StatsGenerate -1,)
19:01:07 Installation Failed.
"Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
> What were the last few successful entries? Do you have an installation
> that WAS successful that you can compare it to?
> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is located
>> in the Windows directory, gives detailed information on what setup is
>> doing and contains all errors encountered during setup. Reviewing this
>> file will give you a better understanding of where setup fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the initial
>> installation scripts. Any error encountered during this process is also
>> written to the Sqlstp.log file; however, you should also review the SQL
>> Server error log, named "Errorlog" with no file extension, located by
>> default in the Program Files\Microsoft SQL Server\Mssql\Log directory.
>> This error log contains errors that SQL Server encounters when setup
>> attempts to start SQL Server, which may provide further insight into the
>> failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own the
>> SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>|||I'm sure one of the MS guys will jump in here somewhere and give you more
than I can. Can you remove the Symantic product as a test?
HTH
Jerry
"aLAMBIKI" <alambiki@.yahoo.com> wrote in message
news:4356c190$1$4337$626a54ce@.news.free.fr...
>I already installed SBS + SQL on this server. It is the second time I
>install it on this server. The only thing that changes is that I updated
>with the latest ms update + installed symantec lifestate...
> here is the log of SQLstp.log
> 19:00:30 Begin Setup
> 19:00:30 8.00.194
> 19:00:30 Mode = Normal
> 19:00:30 ModeType = NORMAL
> 19:00:30 GetDefinitionEx returned: 0, Extended: 0x0
> 19:00:30 ValueFTS returned: 1
> 19:00:30 ValuePID returned: 1
> 19:00:30 ValueLic returned: 1
> 19:00:30 System: Small Business Server
> 19:00:30 SQL Server ProductType: Standard Edition [0x2]
> 19:00:30 Begin Action: SetupInitialize
> 19:00:30 End Action SetupInitialize
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Reading Software\Microsoft\Windows\CurrentVersion\CommonFilesDir
> ...
> 19:00:30 CommonFilesDir=C:\Program Files\Fichiers communs
> 19:00:30 Windows Directory=C:\WINDOWS\
> 19:00:30 Program Files=C:\Program Files\
> 19:00:30 TEMPDIR=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\1\
> 19:00:30 Begin Action: SetupInstall
> 19:00:30 Begin Action: CheckFixedRequirements
> 19:00:30 Platform ID: 0xf000
> 19:00:30 Version: 5.2.3790
> 19:00:30 File Version - C:\WINDOWS\system32\shdocvw.dll: 6.0.3790.2523
> 19:00:31 End Action: CheckFixedRequirements
> 19:00:31 Begin Action: ShowDialogs
> 19:00:31 Initial Dialog Mask: 0x183000f7, Disable Back=0x1
> 19:00:31 Begin Action ShowDialogsHlpr: 0x1
> 19:00:31 Begin Action: DialogShowSdWelcome
> 19:00:32 End Action DialogShowSdWelcome
> 19:00:32 Dialog 0x1 returned: 1
> 19:00:32 End Action ShowDialogsHlpr
> 19:00:32 ShowDialogsGetDialog returned: nCurrent=0x2,index=1
> 19:00:32 Begin Action ShowDialogsHlpr: 0x2
> 19:00:32 Begin Action: DialogShowSdMachineName
> 19:01:07 ShowDlgMachine returned: -1
> 19:01:07 ShowDlgMachine: GetLastError returned: 0
> 19:01:07 Opération réussie.
> 19:01:07 End Action DialogShowSdMachineName
> 19:01:07 End Action ShowDialogs
> 19:01:07 Action CleanUpInstall:
> 19:01:07 StatsGenerate returned: 2
> 19:01:07 StatsGenerate (0x0,0x0,0xf000,0x0,1036,0,0x0,0x0,0,0,0
> 19:01:07 StatsGenerate -1,)
> 19:01:07 Installation Failed.
>
> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
> OdVtGSP1FHA.560@.TK2MSFTNGP12.phx.gbl...
>> What were the last few successful entries? Do you have an installation
>> that WAS successful that you can compare it to?
>> "aLAMBIKI" <alambiki@.yahoo.com> wrote in message
>> news:4356ae9a$0$4336$626a54ce@.news.free.fr...
>> Yes I tried to reinstall after reboot.
>> I found the Sqlstp.log file, but am not able to understand it.
>> If someone has an idea...
>> "Jerry Spivey" <jspivey@.vestas-awt.com> a écrit dans le message de news:
>> enXaUuM1FHA.1264@.tk2msftngp13.phx.gbl...
>> Did you try installing again after the reboot? Was there an error code
>> listed?
>> From KB Article 257716:
>> Q. What should I do if the installation of SQL Server 2000 is
>> unsuccessful?
>> A. If you have an unsuccessful installation, you can examine two files
>> to help determine what went wrong. The Sqlstp.log file, which is
>> located in the Windows directory, gives detailed information on what
>> setup is doing and contains all errors encountered during setup.
>> Reviewing this file will give you a better understanding of where setup
>> fails and why.
>> During the configuration portion of setup, SQL Server setup runs an
>> application called Cnfgsvr.exe to configure the SQL Server. This
>> application starts SQL Server, connects to it, and then runs the
>> initial installation scripts. Any error encountered during this process
>> is also written to the Sqlstp.log file; however, you should also review
>> the SQL Server error log, named "Errorlog" with no file extension,
>> located by default in the Program Files\Microsoft SQL Server\Mssql\Log
>> directory. This error log contains errors that SQL Server encounters
>> when setup attempts to start SQL Server, which may provide further
>> insight into the failure.
>> If you cannot determine the cause of the Setup failure, save the two
>> files just mentioned and call Microsoft Product Support Services (PSS)
>> to speak to a SQL Server Support Professional who will help you to
>> resolve your problem. Note that when the Setup application fails, it
>> rolls back all changes to the file system, which includes removing any
>> copied files and changes that were made to the registry.
>>
>> HTH
>> Jerry
>> "Alambiki" <alambiki@.yahoo.com> wrote in message
>> news:dj5qnl$ok9$1@.reader1.imaginet.fr...
>> Hi,
>> I am trying to install SQL 2000 sevrer on my SBS 2003 server (I own
>> the SBS
>> 2003 server Premium).
>> I installed the OS lately and made all the Microsoft update.
>> I am now trying to install the SQL 2000 server and get this error
>> message:
>> (It is the english translation of what I get on my screen)
>> Error message: "A previous installation program created operation
>> files
>> waiting for Installtion on your computer. You have to reboot it before
>> executing the installation."
>> Of course I rebooted my server, but nothing happened.
>> Any idea of what to do ?
>> Thank you for your help
>>
>>
>>
>sql

Monday, March 12, 2012

Error when clicking OK on edit of task

I've got a package that was imported from SQL 2000 into SQL 2005. I'm trying to edit it in Business Int. Dev Studio. When I open what used to be a data pump step in 2000, I'm able to edit items. However, when I click OK, it puts an error right below the buttons:

"" is not a value type

And it won't let me save my changes. I have no idea where this error is coming from. All the data pumps in this package cause the same error. Your help is appreciated.Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.|||

arc_dev wrote:
Found the solution thanks to our server support staff: They noticed that all the global variables (now referred to as inner variables) were missing their type. They had names and values, but no type. To give them a type, we just needed to change the name of the variable and then change it back -- this caused the type dropdown to become active. Then we had a type for each variable as well. I hope this helps others who run into this same issue.

Well done for picking this up. Did you use the migration wizard? If so, this is a bug in the migration wizard. Could you report it at Microsoft Connect?

-Jamie

|||I just created a bug report with screen captures of what it does.

Sunday, February 19, 2012

Error to install the SQL server Database services

Hay,

I have a problem to in stall my SQL database services.

I use the Microsoft SQL server 2005 on a Microsoft small business server 2003 system.

My system configuration check is oke and i have no problems to install the other services(Analysis,Reporting,Notification and Intergration).

When i install the SQL database services i have this error:

(Error attempting to read from the source install database,

d:\windows\install\7b027f.msi).

thanks

If you scan your install log files you may find more information to help track down the problem. Here's a brief description of where to look and what to look for, copied from Jeffrey Baker's blog but I would look for more anomalies than just "ue 3":

Please look at the file "%ProgramFiles%\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Summary.txt" which should contain a summary of the
installation and what, if any errors there were. If you see an error,
please copy that section back to this thread. Then open up the Log File for
that failure and do a search for "ue 3" and copy a block of text from 10
lines above "ue 3" to 10 lines below "ue 3" back to this thread.

Error Starting Script Editor in SSIS

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:
Cannot show the editor for this task. (Microsoft Visual Studio)
For the Script component I get:
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

|||Those are the only two that I have noticed it in. Are there other objects that have Design Script buttons. If so, I will test them and reply with an answer.|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||I am wondering if anyone is monitoring this forum, I posted answers to the questions that I was asked and haven't received any more responses.|||Well, perhaps a reinstall is in order... Nevermind... Just read the whole thread.|||I was just wondering if this could be happening because this desktop is running Windows XP Media Edition?|||

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... blah blah, and another message saying "interface not registered". Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.

|||

Your idea is on the right path. My initial error pointed me to the DTS folder under C:\Program Files\Microsoft SQL Server\90\DTS\Binn. I registered what you did above, but it did not work. I decided, hey lets try the DTS\Binn folder. What do you know, I no longer get the error and can see all my work flow in SSIS. Thanks for the tip (it appears security does not have to be set to Local User, but rather a solid Admin account).

Thanks,

Error Starting Script Editor in SSIS

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:
Cannot show the editor for this task. (Microsoft Visual Studio)
For the Script component I get:
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when
the integration service does not have sufficient right
in the Box.
check to see if the integrarion service has sufficient rights
click start>run>type "service.msc"
look for the integration service and supply it with a powerful account in your box
perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

|||

Thanks,

Error Starting Script Editor in SSIS

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:
Cannot show the editor for this task. (Microsoft Visual Studio)
For the Script component I get:
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when
the integration service does not have sufficient right
in the Box.
check to see if the integrarion service has sufficient rights
click start>run>type "service.msc"
look for the integration service and supply it with a powerful account in your box
perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

|||

Thanks,

Error Starting Script Editor in SSIS

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

|||

Thanks,

Friday, March 23, 2012

Error when limiting memory usage with OSQL.EXE

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Error when installing SQL server 200 on SBS 2003 in Windows Small Business Server 2003

Monday, March 12, 2012

Error when clicking OK on edit of task

Sunday, February 19, 2012

Error to install the SQL server Database services

Error Starting Script Editor in SSIS

Error Starting Script Editor in SSIS

Error Starting Script Editor in SSIS

Error Starting Script Editor in SSIS

Error running report

Blog Archive

About Me