Hi,
I want set a specific port number of SQL Server(express) during installation not by Configuration Manager after install.
Is it possible?
hi,
probably becouse of the multi instances support of SQL Server up to version 2000, which introduced the SQL Server Resolution Service listening on UDP 1434, now SQLBrowser, this feature has been removed from the configurable settings..
but you can interact via SMO as well, but probably after your installer has finished..
regards
Just curious, I'm reading about the SQL Server 2005 post SP1 hotfix and it looks like you need to install the packages in order:
SQL Server
Analysis Services
Integration Services
Notification Services
Reporting Services
Tools
My desktop is configured as an Analysis Services and Integration Services instance, but without the SQL Server proper components installed. What should my install order be? Does important note 3 about SMO and SQL-DMO still apply?
Thanks,
Keehan
What document do you refer to?
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Sorry 'bout that:
http://support.microsoft.com/kb/918222
Cheers,
Keehan
|||If you didnt install SQL Server relational engine, you should be fine with installing hotfix packges for installed components only.
Looks SQL-DMO issue only applies if you have SQL Server relational engine installed.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. ExactlyThe patch number and KB article are the same. Welcome to Microsoft....|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).
|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. Exactly|||OK, there are 2 different patches for this. One for WinXP, one for Vista - they have
different patching systems. So if you call MS, make sure they know which one you want.
The patch number and KB article are the same. Welcome to Microsoft....
|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?
|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208
|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso
|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).
|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. Exactly|||OK, there are 2 different patches for this. One for WinXP, one for Vista - they have
different patching systems. So if you call MS, make sure they know which one you want.
The patch number and KB article are the same. Welcome to Microsoft....
|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?
|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208
|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso
|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. ExactlyThe patch number and KB article are the same. Welcome to Microsoft....|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).
|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. Exactly|||OK, there are 2 different patches for this. One for WinXP, one for Vista - they have
different patching systems. So if you call MS, make sure they know which one you want.
The patch number and KB article are the same. Welcome to Microsoft....
|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?
|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208
|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso
|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via:
for %i in (*.dll) do RegSvr32 -s %i.
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\
C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
Yes I have similar issue. I cant edit my script component. I am getting an following error message when I click on "Design Script".
Cannot Show Visual Studio for Applications Editor. Engine Returned Unknown Error
Anyone else?
Thanks
Sutha
|||I haven’t seen anything like this. From the look of it the VSA is installed properly (you mentioned that you can start designer for the script task but not for the script component). Can you design new script components on that machine?
Thanks
|||New SP2 script components and tasks can be created and edited.Script components created prior to SP2 (at least those created on 2153 and perhaps earlier) cannot be opened, at least on Windows XP. On Windows 2003 Server (32 or 64 bit) I have not observed any issue (the editor open's fine on the same .dtsx that fails to open on an XP machine).
|||
I have the exact same issue and here is an interesting addition:
If I add a new script component (without attaching it to anything) and attempt to view the script it actually brings up the script editor with the code of the old script component that I was trying to open in the first place.
I guess I'll have to uninstall SP2 at this point.
Daryl
|||If you're on Vista, try the hotfix:This uneditable script component problem is specifically noticed on Windows XP and is unsolved and without reasonable workaround(e.g. total replacement of OS with Win2k3).
The Vista script component create/edit issue is indeed solved with that 931846 hotfix (the receipt of which requires a call to Microsoft PSS as it is not regression tested).
|||I can definitely confirm this exact problem after an install of SS2005 SP2a. Exactly|||OK, there are 2 different patches for this. One for WinXP, one for Vista - they have
different patching systems. So if you call MS, make sure they know which one you want.
The patch number and KB article are the same. Welcome to Microsoft....
|||Are you saying this is resolved? I don't believe it for one second, and I'll happily admit to being wrong. What is the URL, if you would be so kind?
|||I'm having the same problem. Where can I find the XP patch?|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
KB928208
|||Yes, resolved to my satisfaction. I got the WinXP patch and it fixed the problem
and I am working fine now. 2 iterations with MS to get the right one. Vista has
a totally new and different patching mechanism, but the patch underneath is the same.
http://support.microsoft.com/default.aspx/kb/928208
You have to call MS to get this.
|||After two disconnects without being able to talk to anybody, a 90 minute wait time on the third try, and two more hours trying get this error solved, we got it to work. At least, some sort of temp solution until a KB / hotfix is available.
Keep in mind this is for a Win Server 2k3 environment and not exactly the most recommended solution.
Anyways, this was my fix.
Go to your pacakge code ( right click the package in the solution explorer and select view code ). Search for every "ReferencePath" and pretty much replace
""C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.DTSRuntimeWrap\" with "C:\WINDOWS\assembly\GAC_32\Microsoft.SqlServer.DTSRuntimeWrap\". (the rightmost reference)
Viola! That's it!
For now, I'll only do this for the packages I need to edit.
I hope this helps.
Thanks,
Alonso
|||That's what I sent to Microsoft last night ( swap GAC_MSIL to GAC_32 on the reference path) and the 2153 script component starts working. Didn't post that advice on the forum because I wanted to hear back from Microsoft as to whether that was a legitimate solution, indicative of an underlying issue (perhaps with ngen.exe's queue), or both or neither. I understand that its not the most recommended solution, but its the only solution right now.
I had been checking for a Exit Code != 0 to detect errors returned by setup.exe but this does not appear to be foolproof. Several customers' deployments have returned non-zero exit codes, but SQL Express seems to be successfully installed.
I have not found a reference of possible codes returned and their meaning that I could use to fine tune our checking. Does one exist? Or am I going about this the wrong way and should just check for the existence of our instance after setup is complete?
thank you for any input.
I *think* the only other success error code you need to code around is error code 3010, which signifies success, but a reboot is necessary.
Here is a list of other possible Windows Installer error codes:
http://msdn2.microsoft.com/en-us/library/aa368542.aspx
Thanks,
Sam Lester (MSFT)
Hello,
I spent days trying repeatedly to install SQL Server 2005 Express edition and always received an error message. I uninstalled SQL Server 2000, cleaned the registry, uninstalled/reinstalled Visual Basic 2005 Express, read all the forums and tried every combination. I always received this failure message:
The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually." The error is (1067) The process terminated unexpectedly. Error Number : 29503
If this is the particular error you are receiving, then maybe this post will help.
The solution for me was NOT to uninstall Visual Basic 2005 Express Edition, or install SQL Server 2005 in any particular order vs installing VB 2005 Express.
These are the steps that worked for me. Run setup for SQL Server 2005 Express. On the first setup screen, there is a checkbox that says "Hide advanced setup/installation options" (or somesuch). It is checked by default. UNCHECK IT. (You DO want to select advanced options because the defaults are not working for you.)
Look closely at the screens that follow. Look for the dropdown that says "Install SQL Server as a... Network Service. In the dropdown, change the choice to Local Service.
In another screen, look for the Authentication method. Do NOT use Windows authentication, which is the default. Select Mixed Mode authentication, and provide a strong password.
Now, let it install. For me, it no longer failed. SQL Server installed with no further problems.
Hope this helps somebody (including MS in figuring out how come). It worked for me when nothing else did!
SQL Wizard (who?)
SQl Wizard - I am having this exact same issue on my win xp pro sp2 machine. However, I tried what you suggested and still got the same error. I also had sql 2000 installed prior (uninstalled it prior to installing sql 2005) - did you clean up anything in the registry before you started?
Thanks for your help.....
csqlrun
