Hi,
I have a DTS package that I would like to execute from an application
that uses MSDE as it's back end. Is it possible to 'attach' a DTS
package to an MSDE database and execute it from Say example VB.Net.
Any info will be appreciated.
Thanks,
VaughnIf you save a DTS package as VBScript, you should be able to run that
package from a .NET application.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<vaughn.haybittle@.gmail.com> wrote in message
news:1157129984.437055.7530@.e3g2000cwe.googlegroups.com...
> Hi,
> I have a DTS package that I would like to execute from an application
> that uses MSDE as it's back end. Is it possible to 'attach' a DTS
> package to an MSDE database and execute it from Say example VB.Net.
> Any info will be appreciated.
> Thanks,
> Vaughn
>
Showing posts with label package. Show all posts
Showing posts with label package. Show all posts
Friday, March 30, 2012
MSDE and DTS
Hi,
I have a DTS package that I would like to execute from an application
that uses MSDE as it's back end. Is it possible to 'attach' a DTS
package to an MSDE database and execute it from Say example VB.Net.
Any info will be appreciated.
Thanks,
VaughnIf you save a DTS package as VBScript, you should be able to run that
package from a .NET application.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<vaughn.haybittle@.gmail.com> wrote in message
news:1157129984.437055.7530@.e3g2000cwe.googlegroups.com...
> Hi,
> I have a DTS package that I would like to execute from an application
> that uses MSDE as it's back end. Is it possible to 'attach' a DTS
> package to an MSDE database and execute it from Say example VB.Net.
> Any info will be appreciated.
> Thanks,
> Vaughn
>sql
I have a DTS package that I would like to execute from an application
that uses MSDE as it's back end. Is it possible to 'attach' a DTS
package to an MSDE database and execute it from Say example VB.Net.
Any info will be appreciated.
Thanks,
VaughnIf you save a DTS package as VBScript, you should be able to run that
package from a .NET application.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
<vaughn.haybittle@.gmail.com> wrote in message
news:1157129984.437055.7530@.e3g2000cwe.googlegroups.com...
> Hi,
> I have a DTS package that I would like to execute from an application
> that uses MSDE as it's back end. Is it possible to 'attach' a DTS
> package to an MSDE database and execute it from Say example VB.Net.
> Any info will be appreciated.
> Thanks,
> Vaughn
>sql
Wednesday, March 28, 2012
MSDE 2000a Deployment Issues
I need to deploy MSDE 2000a with a custom app built in VB6. I found the
setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
the link I found for MSDE 2000 goes to the same article as 1.0. I've also
seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
clueless about them. What is the best (and hopefully easiest) way to deploy
MSDE 2000 with a custom app built with VB6 using the Package & Deployment
Wizard? Any help would be greatly appreciated.
My advice is don't.
Package the setup program from MS, configure the setup.ini file the way you
want it and get the user to run it. Every other option seems to end up in
pain at present. Much better story coming for SQL Express.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>I need to deploy MSDE 2000a with a custom app built in VB6. I found the
> setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
> the link I found for MSDE 2000 goes to the same article as 1.0. I've also
> seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
> clueless about them. What is the best (and hopefully easiest) way to
> deploy
> MSDE 2000 with a custom app built with VB6 using the Package & Deployment
> Wizard? Any help would be greatly appreciated.
|||Okay, so it sounds like what you're saying is that it's best to include 2
setup programs? First have the user run the setup.exe that comes with MSDE
(with the customized ini file), and then have them run the setup package for
the custom app?
"Greg Low [MVP]" wrote:
> My advice is don't.
> Package the setup program from MS, configure the setup.ini file the way you
> want it and get the user to run it. Every other option seems to end up in
> pain at present. Much better story coming for SQL Express.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "pbb" <pbb@.discussions.microsoft.com> wrote in message
> news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>
>
|||Yep
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:4203C438-9A56-48F0-B36D-22793F26F4AD@.microsoft.com...[vbcol=seagreen]
> Okay, so it sounds like what you're saying is that it's best to include 2
> setup programs? First have the user run the setup.exe that comes with
> MSDE
> (with the customized ini file), and then have them run the setup package
> for
> the custom app?
> "Greg Low [MVP]" wrote:
setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
the link I found for MSDE 2000 goes to the same article as 1.0. I've also
seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
clueless about them. What is the best (and hopefully easiest) way to deploy
MSDE 2000 with a custom app built with VB6 using the Package & Deployment
Wizard? Any help would be greatly appreciated.
My advice is don't.
Package the setup program from MS, configure the setup.ini file the way you
want it and get the user to run it. Every other option seems to end up in
pain at present. Much better story coming for SQL Express.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>I need to deploy MSDE 2000a with a custom app built in VB6. I found the
> setup package to add MSDE 1.0 through the Package & Deployment Wizard, but
> the link I found for MSDE 2000 goes to the same article as 1.0. I've also
> seen a lot of info on using merge modules to deploy MSDE 2000, but I'm
> clueless about them. What is the best (and hopefully easiest) way to
> deploy
> MSDE 2000 with a custom app built with VB6 using the Package & Deployment
> Wizard? Any help would be greatly appreciated.
|||Okay, so it sounds like what you're saying is that it's best to include 2
setup programs? First have the user run the setup.exe that comes with MSDE
(with the customized ini file), and then have them run the setup package for
the custom app?
"Greg Low [MVP]" wrote:
> My advice is don't.
> Package the setup program from MS, configure the setup.ini file the way you
> want it and get the user to run it. Every other option seems to end up in
> pain at present. Much better story coming for SQL Express.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "pbb" <pbb@.discussions.microsoft.com> wrote in message
> news:DDFFD02B-301D-4273-B32B-D6CCFAB50A76@.microsoft.com...
>
>
|||Yep
"pbb" <pbb@.discussions.microsoft.com> wrote in message
news:4203C438-9A56-48F0-B36D-22793F26F4AD@.microsoft.com...[vbcol=seagreen]
> Okay, so it sounds like what you're saying is that it's best to include 2
> setup programs? First have the user run the setup.exe that comes with
> MSDE
> (with the customized ini file), and then have them run the setup package
> for
> the custom app?
> "Greg Low [MVP]" wrote:
MSDE 2000 SP4 Merge Modules
I have a MSDE 2000 InstallShield install package that I've created using the
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
merge modules. I downloaded the SP4 of the desktop engine from the microsoft
site. When downloaded and extracted, there is a folder on my machine
\MSDE\MSM which has all of the merge modules. I've noticed that the SP4
release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and qfepatch.msm.
In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I go
and build I receive the following error: "Error retrieving dependency
MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
why I'm getting this error?
Thanks.
Joanne
hi Joanne
jbayog wrote:
> I have a MSDE 2000 InstallShield install package that I've created
> using the merge modules. I downloaded the SP4 of the desktop engine
> from the microsoft site. When downloaded and extracted, there is a
> folder on my machine \MSDE\MSM which has all of the merge modules.
> I've noticed that the SP4 release has 3 new mm's: msxmlsql32.msm,
> msxmlsqlr32.msm, and qfepatch.msm. In the InstallShield DevStudio
> 9.01 IDE, I check the 3 new mm's. When I go and build I receive the
> following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone
> know why I'm getting this error?
no idea, never used MSDE merge modules, always installed using the setup.exe
boostrap installer.... but have you tried modifying the order of
installation?
http://msdn.microsoft.com/library/de...stsql_8yeq.asp
has not been updated (as BOL in general) at sp4 level, so no additional info
about those new merge modules seems available..
BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
specifies:
"Note Merge modules are not supported for new installations. They are
provided in SP4 for servicing instances of MSDE 2000 that were previously
installed using merge modules."
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I don't know much about MSDE and am just doing some research on it as of
this week.
However, I cam across this link yesterday which might be useful:
http://www.microsoft.com/sql/downloads/2000/sp4.asp
Here is an extract from the site:
"Users who have an existing instance of MSDE 2000 must know how their
instance of MSDE 2000 was installed to know how to update it. In particular,
you must know the original package name for your instance of MSDE 2000. To
determine the original package name, see the article How To Identify Which
MSI File Was Used for an Existing MSDE Installation in the Microsoft
Knowledge Base."
"jbayog" <jbayog@.discussions.microsoft.com> wrote in message
news:8D058312-1747-4A51-A100-FE79DC32C086@.microsoft.com...
>I have a MSDE 2000 InstallShield install package that I've created using
>the
> merge modules. I downloaded the SP4 of the desktop engine from the
> microsoft
> site. When downloaded and extracted, there is a folder on my machine
> \MSDE\MSM which has all of the merge modules. I've noticed that the SP4
> release has 3 new mm's: msxmlsql32.msm, msxmlsqlr32.msm, and
> qfepatch.msm.
> In the InstallShield DevStudio 9.01 IDE, I check the 3 new mm's. When I
> go
> and build I receive the following error: "Error retrieving dependency
> MSXMLSQL1033.996A3FBA_B9BC_4189_9DB1_2B3C86B526BC: 1033 of C:\Program
> Files\InstallShield\DevStudio 9\Modules\i386\MSXMLSQL32.MSM". Anyone know
> why I'm getting this error?
> Thanks.
> Joanne
|||Thanks so much for your help. This an existing MSDE 2000 InstallShield
install package and we have a client who wants to upgrade to SP4 so that is
why I'm trying to build an upgrade for them. I'd like to get rid of using
the MSDE 2000 merge modules per Microsoft's comment. I got it to build by
editing the msxmlsql32.msm and the msxmlsqlr32.msm using the Orca tool. I
think there is a problem with the rows in the ModuleDependency table. I
guess I have the option of building it without these two mm's as our database
application doesn't use xml. I'm a little apprehensive of doing this only
because there is no documentation on these new mm's. I might post to
InstallShield also. Again thanks.
Joanne
Joanne
"Andrea Montanari" wrote:
> hi Joanne
> jbayog wrote:
> no idea, never used MSDE merge modules, always installed using the setup.exe
> boostrap installer.... but have you tried modifying the order of
> installation?
> http://msdn.microsoft.com/library/de...stsql_8yeq.asp
> has not been updated (as BOL in general) at sp4 level, so no additional info
> about those new merge modules seems available..
> BTW, the MSDE readme file, at point 4.2 MSDE 2000 SP4 File location
> specifies:
> "Note Merge modules are not supported for new installations. They are
> provided in SP4 for servicing instances of MSDE 2000 that were previously
> installed using merge modules."
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Monday, March 26, 2012
msde 2000 sp3 install problem on win 2000
server. I am building an installshield package. During this process I must install to win 2000, xp pro etc, at home on my 2000 server I had hell of a time installing the msde. I have tried the msde 2000 sp3 patch as well. The installation rolls back after it is almost done. the log won't tell me anything meaningful. Is there any secret to msde on 2000 severs? I one time managed to install the server after succesfullu monkeying with the security profiles on the server, now it is uninstalled but despite the profile set correctlty I can't install? I need some help FAST!!!
The xp works like a charm.
I have attached the log...so if someone is an expert maybe can shed the ligh for me...Log file is not attached.|||msde setup has a bug - it needs upper case machine id for the network (I wonder if there is a workaround since changing my machine name is not that trivial - I am a cable broadband user.)|||Where did you find out about the upper case machine name - do you have a link ?|||Originally posted by rnealejr
Where did you find out about the upper case machine name - do you have a link ?
? if(document.domain.indexOf('.microsoft.com') > 0) document.domain = 'support.microsoft.com';
Home Search FAQs Downloads Newsgroups Customer Service
Microsoft Knowledge Base Article - 285100
Comments?
Provide us with feedback on this article
Support Centers
Small Business Server
SQL Server
Other Support Options
Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Page Options
Send
Print
FIX: Installation Fails When Windows Computer Name Is Mixed or Lowercase
View products that this article applies to.
This article was previously published under Q285100
BUG #: 351711(SQL2000)
SYMPTOMS
Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.
When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.
When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:
For MSDE 2000:
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:
Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.
CAUSE
GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
File name Platform
-------
SSMSLPCn323 Intel
The following file is available for download from the Microsoft Download Center:
SSMSLPCn323.exe
Release Date: JAN-22-2001
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How To Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
The SSMSLPCn323.exe file contains the following files:
File name Size
EULA.txt 2 KB
Readme.txt 1 KB
SSmsLPCn.dll 29 KB
SSmsLPCn.pdb 73 KB
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
WORKAROUND
To work around this problem, change the computer name to all uppercase characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.
If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.
For SQL Server 2000:
The Sqlstp.log file contains an error message similar to:
2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file:
12:30:08 Name = MYSERVER, Type = 0x1
12:30:08 ComputerName: MyServer
For MSDE 2000:
Run the following command so the installation does not roll back upon failure:
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log
You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.
After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following:
ComputerName =MyServer
The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Last Reviewed: 11/3/2003 (4.0)
Keywords: kbBug kbfix kbQFE KB285100 kbAudDeveloper
Contact Us
? 2003 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility
function thisLoad(){ setcookieval("SITE","GN"); gsfxUpLevel(); g_reSupportedHostnames = new RegExp(".msn.com$|.passport.com$|.xbox.com$|.microsoft.com $|.microsoft.cz$|.msbpn.com$|.microsoft.co.*", "i"); ForeignLink_Hookup(true);LogHit('http://c.microsoft.com/trans_pixel.asp?TYPE=SSPV&SOURCE=SUPPORT&URI=/GN/EN-US/kb_en-us_285100&GUID=1F4FC18C-F71E-47fb-8FC9-612F8EE59C61&R='); } function thisUnload(){ ; }|||The fix is included in the article - do you download the fix ?|||Originally posted by rnealejr
The fix is included in the article - do you download the fix ?
Yes.
The problem is that I do not know how to update the CAB file and I can't even find reference to SSmsLPCn.pdb - I found the dll but I have not replace it yet in the CAB.
I found it incomprehansible that there is this bug and MSFT can NOT provide a decent fix only this weird one that you need to manually update dll's and fix THEIR setup. I have yet to find a reference to fix an existing setup distributable.|||If you follow the instructions in the readme.txt, you should be fine.
The xp works like a charm.
I have attached the log...so if someone is an expert maybe can shed the ligh for me...Log file is not attached.|||msde setup has a bug - it needs upper case machine id for the network (I wonder if there is a workaround since changing my machine name is not that trivial - I am a cable broadband user.)|||Where did you find out about the upper case machine name - do you have a link ?|||Originally posted by rnealejr
Where did you find out about the upper case machine name - do you have a link ?
? if(document.domain.indexOf('.microsoft.com') > 0) document.domain = 'support.microsoft.com';
Home Search FAQs Downloads Newsgroups Customer Service
Microsoft Knowledge Base Article - 285100
Comments?
Provide us with feedback on this article
Support Centers
Small Business Server
SQL Server
Other Support Options
Contact Microsoft
Phone Numbers, Support Options and Pricing, Online Help, and more.
Customer Service
For non-technical assistance with product purchases, subscriptions, online services, events, training courses, corporate sales, piracy issues, and more.
Newsgroups
Pose a question to other users. Discussion groups and Forums about specific Microsoft products, technologies, and services.
Page Options
Send
FIX: Installation Fails When Windows Computer Name Is Mixed or Lowercase
View products that this article applies to.
This article was previously published under Q285100
BUG #: 351711(SQL2000)
SYMPTOMS
Connection attempts over the shared memory network library fail on a server where GetComputerName returns a lower or mixed case server name.
When the shared memory connection attempt fails the SQL Server 2000 network library attempts to connect over an alternate protocol.
When you install any edition of Microsoft SQL Server 2000 or Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) on a computer whose name is all lowercase or mixed case, Setup may fail, and you receive one of the following messages:
For MSDE 2000:
Setup failed to configure the server. Refer to the server error logs and setup error logs for more information.
For SQL Server 2000:
Setup failed to configure the server. Refer to the server error logs and sqlstp.log for more information.
CAUSE
GetComputerName is used to obtain the local computer name. The client network library component (DBMSLPCn.dll) converts the name to all upper case. The server network library component (SSMSLPCn.dll) leaves the name as returned.
RESOLUTION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
File name Platform
-------
SSMSLPCn323 Intel
The following file is available for download from the Microsoft Download Center:
SSMSLPCn323.exe
Release Date: JAN-22-2001
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How To Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
The SSMSLPCn323.exe file contains the following files:
File name Size
EULA.txt 2 KB
Readme.txt 1 KB
SSmsLPCn.dll 29 KB
SSmsLPCn.pdb 73 KB
NOTE: Due to file dependencies, the most recent hotfix or feature that contains the preceding files may also contain additional files.
WORKAROUND
To work around this problem, change the computer name to all uppercase characters.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
MORE INFORMATION
The failure is prohibitive to a SQL Server 2000 setup. A SQL Server 2000 setup prevents external connections by only allowing the shared network library connections.
If a shared memory connection can not be established, the setup fails when it attempts to configure the SQL Server server.
For SQL Server 2000:
The Sqlstp.log file contains an error message similar to:
2:44:57 C:\Program Files\Microsoft SQL Server\80\Tools\Binn\cnfgsvr.exe -F "C:\WINNT\sqlstp.log" -dbdebug -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 262404 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r [Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
In the same Sqlstp.log file you can verify the naming failure by locating the following at the top of the log file:
12:30:08 Name = MYSERVER, Type = 0x1
12:30:08 ComputerName: MyServer
For MSDE 2000:
Run the following command so the installation does not roll back upon failure:
setup.exe /DISABLEROLLBACK=1 /L*v C:\temp\msdesetup.log
You must run this code so that the Cnfgsvr.out file can be collected. Using the /L*v switch enables verbose logging for MSDE 2000 Setup.
After the MSDE 2000 installation fails, when you review the contents of the Cnfgsvr.out file, you see an error message similar to the following:
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=MyServer;UID=sa;PWD=;database=maste r
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
The naming failure can be located from the server parameter. The Msdesetup.log file has an entry similar to the following:
ComputerName =MyServer
The information in this article applies to:
Microsoft SQL Server 2000 (all editions)
Microsoft SQL Server 2000 Desktop Engine (MSDE)
Last Reviewed: 11/3/2003 (4.0)
Keywords: kbBug kbfix kbQFE KB285100 kbAudDeveloper
Contact Us
? 2003 Microsoft Corporation. All rights reserved. Terms of use Security & Privacy Accessibility
function thisLoad(){ setcookieval("SITE","GN"); gsfxUpLevel(); g_reSupportedHostnames = new RegExp(".msn.com$|.passport.com$|.xbox.com$|.microsoft.com $|.microsoft.cz$|.msbpn.com$|.microsoft.co.*", "i"); ForeignLink_Hookup(true);LogHit('http://c.microsoft.com/trans_pixel.asp?TYPE=SSPV&SOURCE=SUPPORT&URI=/GN/EN-US/kb_en-us_285100&GUID=1F4FC18C-F71E-47fb-8FC9-612F8EE59C61&R='); } function thisUnload(){ ; }|||The fix is included in the article - do you download the fix ?|||Originally posted by rnealejr
The fix is included in the article - do you download the fix ?
Yes.
The problem is that I do not know how to update the CAB file and I can't even find reference to SSmsLPCn.pdb - I found the dll but I have not replace it yet in the CAB.
I found it incomprehansible that there is this bug and MSFT can NOT provide a decent fix only this weird one that you need to manually update dll's and fix THEIR setup. I have yet to find a reference to fix an existing setup distributable.|||If you follow the instructions in the readme.txt, you should be fine.
Friday, March 9, 2012
msde
I recently joined a company where they have couple of MSDEs that were
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?
sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?
sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
Wednesday, March 7, 2012
msde
I recently joined a company where they have couple of MSDEs that were
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
installed as part of the software application package. Do they need to be
administered as well alongwith the other Standard and Enterprise SQL Servers
installations?sharman,
The answer about how much administration depends on how these MSDE servers
are being used.
If they hold critical data, then yes they need to be administered along with
the other SQL Servers. If there are security issues related to access, these
need to be managed as well.
If the application simply uses these databases as a temporary workarea and
can easily rebuild the data in case of problems, then the management is
less. It would still be good to have database backups that could restore
the metadata.
You need to understand what is going on with the MSDEs and then you can make
a good decision.
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:1B413580-5393-405C-81CD-0CECD6D4DA83@.microsoft.com...
>I recently joined a company where they have couple of MSDEs that were
> installed as part of the software application package. Do they need to be
> administered as well alongwith the other Standard and Enterprise SQL
> Servers
> installations?
msdb Unavailable
I work on a SQL 2000 Standard server that is part of our SBS package. Two days ago we ran a set of MS updates on the server and the residual symptom is that DTS packages, the Import or Export wizard all will not run. The Sql Server Agent service runs under the local system account, however that was true prior to the updates.
The error when attempting to run an import is that the OLEDB connection object is not available. The error occurs when trying to use the Access driver or a DSN. Further investigation indicates that msdb could not be contacted.
Does anyone have an idea as to what might cause this and a workaround?
Thanks,
misdeanI would perform an integrity check (DBCC CHECKDB) of the MSDE database, to se if it is corrupt. It might be because it's late night here, but that's the only reason I could think of now.|||I will give it a try. Somehow, I believe is is related to the MS updates applied the other day. I will run DBCC on it in the AM and post the results.
Thanks,
Keith
The error when attempting to run an import is that the OLEDB connection object is not available. The error occurs when trying to use the Access driver or a DSN. Further investigation indicates that msdb could not be contacted.
Does anyone have an idea as to what might cause this and a workaround?
Thanks,
misdeanI would perform an integrity check (DBCC CHECKDB) of the MSDE database, to se if it is corrupt. It might be because it's late night here, but that's the only reason I could think of now.|||I will give it a try. Somehow, I believe is is related to the MS updates applied the other day. I will run DBCC on it in the AM and post the results.
Thanks,
Keith
Saturday, February 25, 2012
msdb Restore......
I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
Benjamin
Dear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default...b;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>
|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/...ent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
Benjamin
Dear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default...b;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>
|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/...ent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
msdb Restore......
I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent/sp_sqlagent_rename.sql
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
msdb Restore......
I have restored the production msdb database on a test box. I can see my
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/defaul...kb;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedule
s)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent...gent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
entire DTS package and the scheduled jobs.
When I try to modify the job I am getting the following error.
Error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSZSERVER. The job was not saved. OK Button
How to delete/update then?
SQL 2K.
Thank you,
BenjaminDear Benjamin,
Is the server was renamed from one name to another, if so see the
logins were in sync, another work around is
The best way to handle this problem after the rename process is to follow
these steps: 1. Rename the server back to the original name.
2. Script out all of the jobs and then delete them.
3. Rename the server to the new name.
4. Add back the jobs by running the script generated from step 2.
Or
1.Script the jobs in the server from where u backed up the msdb database.
2.Run the scripts in the new server.
for more details go through the following kb site
http://support.microsoft.com/defaul...kb;en-us;281642
"Benjamin Nethan" wrote:
> I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or schedule
s)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
>|||You need to update the originating_server column in sysjobs to reflect the
name of the instance you restored the database to. You can use the following
code to do that http://sqldev.net/download/sqlagent...gent_rename.sql
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Benjamin Nethan" <BNethan@.hotmail.com> wrote in message
news:e59AAE5pFHA.820@.TK2MSFTNGP09.phx.gbl...
>I have restored the production msdb database on a test box. I can see my
> entire DTS package and the scheduled jobs.
> When I try to modify the job I am getting the following error.
> Error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSZSERVER. The job was not saved. OK Button
> How to delete/update then?
> SQL 2K.
> Thank you,
> Benjamin
>
>
msdb or file system
When I log into Integrated Services on my SQL server, I see [Stored Package] -- File System and MSDB.
When I deploy/import my SSIS packages which should it go under? Is there a difference and if so what the difference?
thanks
HAHAHA! You asked the exact same question as someone else and within something like two hours.http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2008865&SiteID=1
Since that question is unanswered, here's the deal.
Where you ultimately choose to store your packages, is up to you. They each do the same thing, but with some differences.
With File System storage, you can simply map a network drive to the server and just copy your packages over to the server. With SQL Server, you need to import into MSDB.
Some like to use File System, but to me, the permissions are harder to work with. Because SSIS does not save passwords, you'll have to use a configuration file to specify passwords for your connection managers. Either that, or you'll have to use EncryptSensitiveWithPassword and then specify a decryption password with the command line.
SQL Server has the same problems unless you tell it to use "SQL Server Roles and Storage" when importing. This is what I choose to use. Access is controlled via SQL Server roles/security.
Search this forum for other ideas regarding file system versus MSDB.|||
LOL
thanks, I'm not a big fan of using the file system for much and due to the permissions within the tool then going through the act of congress to get permissions setup on a network drive to use, isn't worth the hassle.
It would take me longer to get that setup (just from the network side) then it would for me to create a package, test it, import it and roll it out to production and create 10 more.
So I think I'll go the MSDB route.
|||More information:http://blogs.conchango.com/jamiethomson/archive/2006/02/20/SSIS_3A00_-Deploy-to-file-system-or-SQL-Server.aspx
http://www.sqljunkies.com/WebLog/knight_reign/archive/2005/05/05/13523.aspx|||
thanks, I was just reading the sqljunkies.com one actually.
So far I'm not finding a clear cut answer, I guess it really depends on the person deploying the packages.
its kind of like, what language is better C# or VB.NET? no clear answer, its developer preference.
thanks again
Subscribe to:
Posts (Atom)