Quantcast
Channel: SQL Server Setup & Upgrade forum
Viewing all 5760 articles
Browse latest View live

SSMA - Changing Packaged Types

$
0
0

I need to make minor changes to my Oracle packages to properly resolve ROWTYPE.  SSMA for Oracle V6 allows me to change Packaged Functions and Packaged Procdures, but not Packaged Types.  I'd like to change the following statement

TYPE gv_table1_address_type IS TABLE OF table1%ROWTYPE INDEX BY PLS_INTEGER;

to

TYPE gv_table1_address_type IS TABLE OF schema1.table1%ROWTYPE INDEX BY PLS_INTEGER;

How can I change/edit my Packaged Types?


SQL Server Service Pack 2

$
0
0

Hello All,<o:p></o:p>

I am new using the SQL Server, i am trying to install the SP 2 but i am getting and this error message: There are no SQL Server instances or shared features that can be updated on this computer…<o:p></o:p>

I’ve tried to install it twice (removing it each time) , but I am still not able to get this to work on my PC. <o:p></o:p>

I hope you can give me some help! <o:p></o:p>

Regards!<o:p></o:p>

Upgrading from SQL Server 2008 R2 SP2 to SQL 2012

$
0
0

Hi,

I have evaluation copy of SQL 2008 R2 SP2 Enterprise edition installed. 

Now I want to upgrade it to SQL 2012 but everytime it fails at Upgrade Rules step: This version cannot be upgraded from the specified edition. I have tried all flavors but no luck.

Please help. 

Transreplicator tool for Windows 7 machine

$
0
0

Hi,

I would like to use Transreplicator Tool (http://www.transreplicator.com/home.shtm) for windows 7 machine with SQL server 2008 version for DB comparison.

Anyone can help me whether Win7 machine will support Transreplicator tool.

firewall issue with SQL

$
0
0

I have a named sql instance on SQL 2012. The issue is that the clients is having problem connecting to it when the firewall is on, this is not consistent. The connection is fine when I disabled the firewall. When I turned the Windows firewall back on, it will work for awhile and it fails. I checked the SQL configuration manager and saw that a dynamic port is assigned to the named instance. I did put that in the firewall rule and unblock it. I also put TCP 1433 and 1434 as well as the browser service port, TCP\UDP 2382 and it still didn't work.

What is the best way to determine what port does the named instance are listening?

Thanks

Windows Server 2008 R2 DataCenter + Sql 2008 install leads to CAS Policy error

$
0
0

I created a new Windows Server 2008 R2 SP1 DataCenter VM using a Microsoft Azure image

I enabled the .NET 351 Framework via Features in Service Manager and installed IE11 (as I needed to download a file from OneDrive)

As soon I began to install sql 2008 I received this error:

"Microsoft.NET Framework CAS Policy Manager has stopped working"

Problem signature:  BEX64
Application Name:   caspol.exe
Application version: 2.0.50727.5483
Fault module Name:  System.Data.Dll


The odd part is I did this very same install on an Azure Windows VM 3 or 4 months ago and it worked fine.
Any ideas much appreciated.

edm2

Installed 2014 developer edition but SSMS says license has expired

$
0
0

Installed SQL Server 2014 to evaluate it. The evaluation has expired. I uninstalled SQL Server 2014. Via my MSDN subscription I downloaded the Developers edition for SQL Server 2014.

It installed ok but SSMS.exe says that the evaluation period has expired.

---------------------------
Microsoft SQL Server Management Studio
---------------------------
Evaluation period has expired. For information on how to upgrade your evaluation software please go to http://www.microsoft.com/sql/howtobuy
---------------------------
OK   
---------------------------

I don't want to buy it I have the developers edition and I want to use it to develop with not use in a commercial sense.


I tried following the advice here https://support.microsoft.com/en-us/kb/971268?wa=wsignin1.0 even though it is for an older version. Didn't work.

I now as a consequence have 2 named instances of SQL Server 2014 but can't play with either of them due to SSMS being expired.

How can one fix this short of nuking my notebook and starting again which I won't do?

The SQL Server Network Interface library could not deregister the Service Principal Name.

$
0
0

Hi, 

We have installed on two brand new Windows Server 2012 R2, one for TFS 2015 application tier and one for SQL 2014 with SP1.

We copy the DB from a TFS 2012 and upgraded it to TFS 2015.

Everything worked fine for almost 10 days, than users started to get the TF53001: The database operation was canceled by an administrator.

We look at the events on the server which host TFS 2015 application tier.

The first TF53001 was associated to the exception message: Target principal name is incorrect, Cannot generate an SSPI Context.

After trying to find a solution for an hour, since we have 300 users which are waiting for the service to come back, we decided to reboot both servers.

During the shutdown of the SQL server, we found in the log the following messages: The SQL Server Network Interface library could not deregister the Service Principal Name (SPN) [MSSQL.Svc/our.server.name] for the SQL Server service. Error: 0xffffffff, state 63. Administrator should deregister this SPN manually to avoid client authentication errors.

Since the reboot (last friday), both servers look to be working fine, but we don't know what cause the problems and how to prevent the issue to reappear again?

After publishing the question on the TFS Forum, they think it's more an SQL issue.

Regards,

Huy


Is it even possible to exchange retail DVD media for SQL 2014 Standard?

$
0
0

Our company purchased a boxed retail variant of MS SQL Server 2014 Standard with 10 CAL. Original product delivered from reseller, problem is the DVD media is faulty and cannot be read on 4 different PCs.

 

I contacted store and they told me to call Microsoft as reseller’s policy prohibits them from replacing open-box software products.

Called Microsoft Software and Hardware Support line, ended up talking to a dozen people in 6 different departments, getting transferred somewhere else forever. Wasted already around 6 hours on this and nobody can help, unless we call “Professional Support” and open a ticket for $250 per incident … just to exchange worthless DVD media. Another advice I heard was to contact reseller again as they are supposed to replace it (they say they don’t).

 

Looks like one may spend $3k on a commercial piece of software and still be unable to use it (physical installation media is faulty) and everybody involved washes their hands off.

 

Even tried contacting MS Store seeing they have SQL 2014 STD as Download option thinking maybe they can give me a link to copy of media (we already have the product key, right?), but learned that we would have to purchase it first …

 

So, is it even possible to exchange retail DVD media for SQL 2014 Standard edition? Our company is not a Volume Licensing customer, so the VL department won’t help us with their downloadable links.

Upgraded from SQL Express 2012 to SQL Express 2012 Standard but still can't start agent

$
0
0

Hi,

I did an in-place upgrade of my SQL Express 2012 to SQL Express 2012 Standard. The database is working fine and can be accessed, but I still cannot start the SQL Agent.  The sql server agent started and then stopped. I made sure that in Management Studio, security, server roles, I have the Network Service account that the SQL Agent is trying to run under, listed with sysadmin rights.

I get the error message in the SQL Agent log:

The edition of SQL Server that installed this service does not support SQL Server Agent.

Which is probably true - the SQL Express version installed the service originally.  How do I get it to recognize that I upgraded?  I went into Server Configuration Tools and enabled it there, then tried starting it but it still just says it started and stopped.

Thanks,

Paul

Any way to prevent members of SQLAgentOperatorRole from creating jobs?

$
0
0

I need some people to have access to troubleshoot/start/stop SQL jobs their accounts wont own in SQL 2014.  To do this I've granted role membership to SQLAgentOperatorRole in msdb and revoked EXECUTE on sp_add_job, however anyone with membership to the operator role can still create jobs.

Is there no way to override the rights provided by SQLAgentOperatorRole?  Or is there a way to provide members of SQLAgentReaderRole the ability to start/stop jobs they don't own as well as prevent them from creating their own jobs?

Just trying to baton down the hatch for SQL security.  Any help is appreciated.  Thanks.

Virtual Account is having problem to SPN registration automaticallly

$
0
0

I'm using SQL 2014 x64. The service account for db service is on NT Service\MSSQLSERVER. It is what Microsoft recommended virtual account but having problem in SPN registration. Here is the error

The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/[my srerver FQDN] for the SQL Server service. Windows return code: 0xffffffff, state: 63. Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually registered.

Had in touch /w my domain admin, he managed to register manually and I see that SPN registered when "setspn -l [my server name]"

Virtual account is purposed eliminating the need for an administrator to manually the SPN, why it is so hard to get the SPN registered and not too many articles for troubleshooting

https://msdn.microsoft.com/en-us/library/ms143504%28v=sql.110%29.aspx#VA

When I restart my db service, the same error remains.

Please help.


Help me please!! i cant install Microsoft SQL Server CLR Types, R2 Object Managements and SQL Express Service Pack 1 x86

$
0
0

help me please... i need it badly... i cant install Microsoft SQL Server System CLR Types, Microsoft SQL Server 2008 R2 Management Objects and Microsoft SQL Server 2008 Express Service Pack 1 x86... i dont know why...

Here is the Error Log:

[09/26/15,13:18:34] Microsoft SQL Server System CLR Types: [2] WARNING! Setup Failed for optional component Microsoft SQL Server System CLR Types. MSI returned error code 1603
[09/26/15,13:18:37] Microsoft SQL Server 2008 R2 Management Objects: [2] WARNING! Setup Failed for optional component Microsoft SQL Server 2008 R2 Management Objects. MSI returned error code 1603
[09/26/15,13:21:25] Microsoft SQL Server 2008 Express Service Pack 1 (x86): [2] Error code -2068643839 for this component is not recognized.
[09/26/15,13:21:26] Microsoft SQL Server 2008 Express Service Pack 1 (x86): [2] Component Microsoft SQL Server 2008 Express Service Pack 1 (x86) returned an unexpected value.
***EndOfSession***

i dont know what to do. please help me.

Problem w/ clusters when trying to install SQL 2014

$
0
0
tried to install SQL server 2014 but it said I had clusters and wasn't online and wouldn't let me continue until I fixed it.  I have no clue what a cluster is. please don't give me answers I can't understand or follow.  Thank you

Can't install sql server 2014 og management

$
0
0

Hi

I´ve been trying to install sql server and management, but it fails every time or gives the error msg that it´s already have been installed..
And can't delete anything either.. 

Error msg: TITLE: Microsoft SQL Server 2014 Setup ------------------------------ The following error has occurred: Den angivne tjeneste findes ikke som en installeret tjeneste. Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x4E01BCF2%25400xDC80C325 ------------------------------ BUTTONS: &Retry Cancel ------------------------------

Log

Overall summary:
  Final result:                  Failed: see details below
  Exit code (Decimal):           -2068119551
  Start time:                    2015-09-27 20:56:04
  End time:                      2015-09-27 21:08:44
  Requested action:              Install

Setup completed with required actions for features.
Troubleshooting information for those features:
  Next step for SQLEngine:       Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Next step for Replication:     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.


Machine Properties:
  Machine name:                  JIMMY
  Machine processor count:       8
  OS version:                    Windows 8
  OS service pack:               
  OS region:                     United States
  OS language:                   dansk (Danmark)
  OS architecture:               x64
  Process architecture:          64 Bit
  OS clustered:                  No

Product features discovered:
  Product              Instance             Instance ID                    Feature                                 Language             Edition              Version         Clustered  Configured
  SQL Server 2014      SQLEXPRESS           MSSQL12.SQLEXPRESS             Database Engine Services                 1033                Express Edition      12.0.2000.8     No         Yes       
  SQL Server 2014      SQLEXPRESS           MSSQL12.SQLEXPRESS             SQL Server Replication                   1033                Express Edition      12.0.2000.8     No         Yes       
  SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services                 1033                Express Edition      12.0.2000.8     No         Yes       
  SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication                   1033                Express Edition      12.0.2000.8     No         Yes       
  SQL Server 2014                                                          Management Tools - Basic                                                          12.0.2000.8     No         No       
  SQL Server 2014                                                          Management Tools - Complete                                                       12.0.2000.8     No         No       
  SQL Server 2014                                                          Client Tools Connectivity                                                         12.0.2000.8     No         No       
  SQL Server 2014                                                          Client Tools Backwards Compatibility                                              12.0.2000.8     No         No        
  SQL Server 2014                                                          Client Tools SDK                                                                  12.0.2000.8     No        No        

Package properties:
  Description:                   Microsoft SQL Server 2014 
  ProductName:                   SQL Server 2014
  Type:                          RTM
  Version:                       12
  SPLevel:                       0
  Installation location:         C:\Users\Jimmy\Downloads\SQLEXPR_x64_ENU\x64\setup\
  Installation edition:          Express

Product Update Status:
  None discovered.

User Input Settings:
  ACTION:                        Install
  ADDCURRENTUSERASSQLADMIN:      true
  AGTSVCACCOUNT:                 NT AUTHORITY\NETVÆRKSTJENESTE
  AGTSVCPASSWORD:                *****
  AGTSVCSTARTUPTYPE:             Disabled
  ASBACKUPDIR:                   Backup
  ASCOLLATION:                   Latin1_General_CI_AS
  ASCONFIGDIR:                   Config
  ASDATADIR:                     Data
  ASLOGDIR:                      Log
  ASPROVIDERMSOLAP:              1
  ASSERVERMODE:                  MULTIDIMENSIONAL
  ASSVCACCOUNT:                  <empty>
  ASSVCPASSWORD:                 <empty>
  ASSVCSTARTUPTYPE:              Automatic
  ASSYSADMINACCOUNTS:            <empty>
  ASTEMPDIR:                     Temp
  BROWSERSVCSTARTUPTYPE:         Disabled
  CLTCTLRNAME:                   <empty>
  CLTRESULTDIR:                  <empty>
  CLTSTARTUPTYPE:                0
  CLTSVCACCOUNT:                 <empty>
  CLTSVCPASSWORD:                <empty>
  CLTWORKINGDIR:                 <empty>
  COMMFABRICENCRYPTION:          0
  COMMFABRICNETWORKLEVEL:        0
  COMMFABRICPORT:                0
  CONFIGURATIONFILE:             
  CTLRSTARTUPTYPE:               0
  CTLRSVCACCOUNT:                <empty>
  CTLRSVCPASSWORD:               <empty>
  CTLRUSERS:                     <empty>
  ENABLERANU:                    true
  ENU:                           true
  ERRORREPORTING:                true
  FEATURES:                      SQLENGINE, REPLICATION, SNAC_SDK
  FILESTREAMLEVEL:               0
  FILESTREAMSHARENAME:           <empty>
  FTSVCACCOUNT:                  <empty>
  FTSVCPASSWORD:                 <empty>
  HELP:                          false
  IACCEPTSQLSERVERLICENSETERMS:  true
  INDICATEPROGRESS:              false
  INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
  INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
  INSTALLSQLDATADIR:             <empty>
  INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
  INSTANCEID:                    SQLSERVEREN
  INSTANCENAME:                  SQLSERVEREN
  ISSVCACCOUNT:                  NT AUTHORITY\Network Service
  ISSVCPASSWORD:                 <empty>
  ISSVCSTARTUPTYPE:              Automatic
  MATRIXCMBRICKCOMMPORT:         0
  MATRIXCMSERVERNAME:            <empty>
  MATRIXNAME:                    <empty>
  NPENABLED:                     0
  PID:                           *****
  QUIET:                         false
  QUIETSIMPLE:                   false
  ROLE:                          AllFeatures_WithDefaults
  RSINSTALLMODE:                 DefaultNativeMode
  RSSHPINSTALLMODE:              DefaultSharePointMode
  RSSVCACCOUNT:                  <empty>
  RSSVCPASSWORD:                 <empty>
  RSSVCSTARTUPTYPE:              Automatic
  SAPWD:                         <empty>
  SECURITYMODE:                  <empty>
  SQLBACKUPDIR:                  <empty>
  SQLCOLLATION:                  Danish_Norwegian_CI_AS
  SQLSVCACCOUNT:                 NT Service\MSSQL$SQLSERVEREN
  SQLSVCPASSWORD:                <empty>
  SQLSVCSTARTUPTYPE:             Automatic
  SQLSYSADMINACCOUNTS:           JIMMY\Jimmy
  SQLTEMPDBDIR:                  <empty>
  SQLTEMPDBLOGDIR:               <empty>
  SQLUSERDBDIR:                  <empty>
  SQLUSERDBLOGDIR:               <empty>
  SQMREPORTING:                  true
  TCPENABLED:                    0
  UIMODE:                        AutoAdvance
  UpdateEnabled:                 true
  UpdateSource:                  MU
  USEMICROSOFTUPDATE:            false
  X86:                           false

  Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150927_205601\ConfigurationFile.ini

Detailed results:
  Feature:                       Database Engine Services
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred during the setup process of the feature.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84BB0001
  Error description:             Den angivne tjeneste findes ikke som en installeret tjeneste.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x4E01BCF2%400xDC80C325&EvtType=0x4E01BCF2%400xDC80C325

  Feature:                       SQL Server Replication
  Status:                        Failed: see logs for details
  Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
  Component name:                SQL Server Database Engine Services Instance Features
  Component error code:          0x84BB0001
  Error description:             Den angivne tjeneste findes ikke som en installeret tjeneste.
  Error help link:               http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x4E01BCF2%400xDC80C325&EvtType=0x4E01BCF2%400xDC80C325

  Feature:                       SQL Writer
  Status:                        Passed

  Feature:                       SQL Client Connectivity
  Status:                        Passed

  Feature:                       SQL Client Connectivity SDK
  Status:                        Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150927_205601\SystemConfigurationCheck_Report.htm



Where can I get SQL 2005 Standard 32 bits?

$
0
0

Hello, we are migrating an existin Windows server 2000 to Windows server 2008 32 bits. We have managed to upgrade W2000 to W2008 and it is working fine, but we have some problems with SQL 2000, and I am afraid that they are caused by incompatibilities between SQL 2000 and W2008, so We though to upgrade SQL 2000 to 2005, but we only have 64 bit version of SQL 2005. We have tried to get the 32 bit version in the oficial download webs but it is no longer available to download.

Can you please tell me if it still possible to get it and where?.

Best regards and thank yoy very much in advance.

2014 SQL Upgrade Advisor timeout errors

$
0
0

We're planning to do an in-place upgrade of our SQL 2008 R2 Standard 64-bit server to SQL 2014 Enterprise 64-bit. Prior to the actual upgrade we ran the SQL 2014 Upgrade Advisor and it came back with the following timeout errors:

Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.SOUNDEX
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.UTF16XQUERY
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.SQLMAIL
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.WARNFNCHANGE
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.COLONUSE
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.MERGE

Are these timeout errors of any significance or can we proceed with the upgrade?

Set up TLS V1.2

$
0
0

hi,

I have been trying to get encryption working on TLSV1.2. I the version of MSSQL which should support TLSV1.2 according to this:

   http://support.microsoft.com/en-us/kb/3052404

Checking with wiresharks show are are using TLSV1.

What are the steps for ensuring we restrict to using TLSv1.2?

Thanks

Paul

SQL 2014 SP1 Upgrade Issues (KB3058865)

$
0
0

We are attempting to test the SQL 2014 SP1 upgrade (KB3058865)  in our test environment, but are unable to complete the upgrade and start the instance. 2 of the 3 instances upgraded fine, the 3rd is failing with events 17063, 912 and 3417. This is similar to the previous SP1 patch that was pulled, but it's a different script failing. SSIS is installed with 1 catalog in the SSISDB.

Script level upgrade for database 'master' failed because upgrade step 'ISServer_upgrade.sql' encountered error 6528, state 1, severity 16.

I have brought the instance back online with the -T902 flag, and now the SSISDB is in single user mode. Since this is the latest correct SP1 install, and a different script failing, I'm not sure what the fix/workaround is in this situation.

Downgrade Business Intelligence 2012 to Standard 2014

$
0
0

Hi

I wanted to upgrade our sql server.  Apparently we had a SQL 2012 business intelligence.  We are not using any of BI features. When installing 2014, the installwizard stops on "FeatureUpgradeMatrixCheck : Checks whether the specified feature meets SQL Server 2014 upgrade requirements." 

(extra info: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2014 version and edition upgrade in Books Online.)

How can I force a downgrade without having to run 2 sql servers next too each other and moving all db's manually?


Dampee (blog | twitter)

Viewing all 5760 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>