Users using Windows Authentication unable to login after upgrade to SQL Server 2012 SP2 CU1
We upgraded from SQL Server 2008 R2 to SQL Server 2012 SP2 CU1. Upgrade was successful. Users that have SQL Server Management Studio 2012 can successfully log in via Windows Authentication, but users with an older version of SQL Server Management
Studio are unable to log in via Windows Authentication.
The error they receive is listed below:
Connect not connect to XXXXXXX
Login Failed. The login is from an untrusted domain and cannot be used with Windows Authentication.
(Microsoft SQL Server, Error: 18452)
If we switch to Mixed authentication, users can log in via SQL Server Authentication.
Our security policy prohibits SQL Authentication.
Outside of having the staff upgrade to SQL Server 2012 SQL Server Management Studio, is there any setting I can set/unset to allow older version of SQL Server Management studio to connect to SQL Server 2012?
Thanks.
DJ
Glad to see that you were able to resolve the issue yourself, but for the curious, could you explain what this
Extended Protection is?
Erland Sommarskog, SQL Server MVP, [email protected]
Similar Messages
-
Package Failing after update to SQL Server 2012 SP2
I have a package that was running fine with SQL Server 2012 until an upgrade to SP2 the package now fails in a derived column step where a bunch of type casts are done
(DT_NTEXT)"\" " + (DT_NTEXT)@[User::phantomScriptLoc] + (DT_NTEXT)"getautomatedtable.js " + (DT_NTEXT)"--ignore-ssl-errors=yes -user \"" + (DT_NTEXT)Username + (DT_NTEXT)"\" -pass \"" + (DT_NTEXT)Password + (DT_NTEXT)"\" -url \"" + (DT_NTEXT)@[User::gatewayWebLoc] + (DT_NTEXT)"\" -module \"/" + (DT_NTEXT)module_name + (DT_NTEXT)"/index.cfm\" -reportpage \"" + (DT_NTEXT)report_name + (DT_NTEXT)"\" -deptid \"" + (DT_NTEXT)cast_deptid + (DT_NTEXT)"\" -reportname \"" + (DT_NTEXT)report_title + (DT_NTEXT)"\" -outfile \"" + (DT_NTEXT)@[User::storeReportsLoc] + (DT_NTEXT)filename + (DT_NTEXT)"\" -format \"" + (DT_NTEXT)RTRIM(AutoRpt_FileFmt_Txt) + (DT_NTEXT)"\" -querystring \"" + (DT_NTEXT)queryString + (DT_NTEXT)"&debugMode=1\"\""
The package does not return an error but instaed call SQLDUMPER and creates a dump file.
Any one else had an issue since an SP2 upgrade?Hi tbrown10a,
I am able to reproduce the issue after installing SP2 for SQL Server 2012. The issue occurs when trying to cast one data type to DT_NTEXT or DT_TEXT data type. As Arthur mentioned, I would suggest you file a connect at
https://connect.microsoft.com/sql.
Connect site is a connection point between you and Microsoft, and ultimately the larger community. Your feedback enables Microsoft to make software and services the best that they can be, and you can learn about and contribute to exciting projects.
Regards,
Mike Yin
TechNet Community Support -
Use of PVKConverter with SQL Server 2012 SP2
I am trying to convert a certificate that was exported from our database server to be used by SQL Server for database encryption. When I run the PVKConverter, not Private Key File (PVK) is generated.
The certificate has Server and Client Authentication as the purposes of the certificate.
What purpose or purposes does the certificate need in order to be able to be used by SQL Server 2012 SP2?
Why doesn't the PVKConverter generate a private key file?
I can use the command makecerts to generate a self signed certificate and have it work with SQL Server database encryption.
Thanks.
DJHi DJ,
Based on my research, SQL Server supports the importing of existing security certificates, specified as a pair of files that are encoded in PVK/DER format. Below Transact-SQL script displays the basic key file format for SQL Server database encryption.
CREATE CERTIFICATE <Certificate name>
FROM FILE = '<PVK/DER format file>.cer'
WITH PRIVATE KEY (FILE = '<PVK/DER format file>.pvk',
DECRYPTION BY PASSWORD = '<Encryption password>');
According to your description, PVKConverter doesn’t generate a private key file. PVKConverter is used to generate PVK/DER encoded security certificates from existing PFX encoded security certificates. Thus, please ensure that your certificate is encoded in
PFX format and make sure you perform all the steps properly as described in the
KB article.
There is also a related blog for your reference.
http://blogs.msdn.com/b/sql_pfe_blog/archive/2014/02/04/generating-a-trusted-tde-certificate-in-the-proper-format-from-a-certificate-authority.aspx
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014
Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCPHi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP -
Reports quit working after upgrade to SQL Server 2008
Folks,
I'm running Visual Studio 2008 (sp1) and recently upgraded to SQL Server 2008. Reports worked fine until after upgrade. Now I get the "Login Failed" error message.
Here is code snippets:
CrystalDecisions.CrystalReports.Engine.ReportDocument oReport = new CrystalDecisions.CrystalReports.Engine.ReportDocument();
TableLogOnInfo LonOnInfo = new TableLogOnInfo();
TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
private Tables crTables;
private Table crTable;
ConnectionInfo crConnectionInfo = new ConnectionInfo();
crConnectionInfo.IntegratedSecurity = true;
crConnectionInfo.ServerName = Properties.Settings.Default.InstanceName + "
Instance";
crConnectionInfo.DatabaseName = "DATABASE";
crTables = oReport.Database.Tables;
for (int i = 0; i < crTables.Count; i++)
crTable = crTables<i>;
crtableLogoninfo = crTable.LogOnInfo;
crtableLogoninfo.ConnectionInfo = crConnectionInfo;
crTable.ApplyLogOnInfo(crtableLogoninfo);
oReport.RecordSelectionFormula = xFormula;
crystalReportViewer1.ReportSource = oReport;
Has anyone had this problem? Any help would be appreciated.
TerryCR 2008 does not support MS SQL 2008 yet, meaning we have not had time to test it completely and add it to our supported platforms.txt file.
One thing I noticed is you are using trusted authenication:
crConnectionInfo.IntegratedSecurity = true;
Make sure you give access to all users, MS changed the security properties a lot since SQL 2005 and you can't simply log into any database now. If you have a DBA check with that person on how to configure NT Authentication or the Help file. You can also do a quick test and simply use MS SQL Server authentication to confirm if it's a user permission issue.
Try creating a report that doesn't use Integrated Security, check the box off on your data logon prompt in the Designer. -
Error in CLR assembly after migrating to SQL server 2012
We moved to SQL Server 2012 from 2008R2 and I am unable to get the CLR assembly working. I have read several topics about trustworthy setting and a mismatch dbo SID. I checked the SID and everything looks good and the 2008R2 server works fine with
Trustworthy set to OFF. I'm starting to think it is a .NET issue. 2008R2 works with 2.0 and 2012 uses 4.0 and i'm wondering if just redeploying the assembly will fix the problem. Any suggestions would be greatly appreciated.
Msg 10314, Level 16, State 11, Procedure MP_ExportXYToCSV2, Line 41
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65540. The server may be running out of resources, or the assembly may not be trusted with PERMISSION_SET = EXTERNAL_ACCESS or UNSAFE. Run the query again, or check documentation
to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly 'exporttocsv, Version=1.0.4780.25878, Culture=neutral, PublicKeyToken=f5567e386ca8280d' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
System.IO.FileLoadException:
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection,
Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)It is not clear what you have done, for an assembly with a permission set beyond SAFE to work, one of these conditions must be set:
1) The database is trustworthy and the database owner has EXTERNAL ACCESS ASSEMBLY or UNSAFE ASSEMBLY permission, depending on the permission set for the assembly.
2) The assembly is a signed with a key, and that key exists in the master database. A login has been created from the key, and this login has been granted the matching assembly permission.
Since you say that it worked on SQL 2008 R2 without trustworthy, I would assume that you had a key-login pair on the old server, but forgot to move them to the new server.
Don't set the database trustworthy. This is a potential security risk.
Erland Sommarskog, SQL Server MVP, [email protected] -
SSIS packages are failing after upgrade to SQL server 2014
Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari -
After upgrade from SQL Server to SQL server 2012 I cannot show Query Designer ?? Please help
Hi
I have installed the required .Net software, but never the less I've got this message. Could you please help me out ?
Thanx in advance
Pia
TITLE: Microsoft SQL Server Management Studio
Cannot show Query Designer.
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
Unable to find the requested .Net Framework Data Provider. It may not be installed. (System.Data)
BUTTONS:
OKalso check
http://connect.microsoft.com/VisualStudio/feedback/details/652192/visual-studio-2010-add-connection-fails
mostly machine.config is referring to .net 3.0 assemblies
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle -
Unable to add replication feature in sql server 2012 web edition
Hi All,
We are using SQL Server 2012, Web edition and when it was installed replication is not an added feature so I tried to add this feature but getting below error.
Error: There are no SQL Server instances or shared features that can be updated on this computer.
Description: The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update. The installed SQL Server product version is 11.1.3000.0, and the expected SQL Server version is 11.0.2100.60
And also please let me know how to identify the default file location of the setup file 'setup.exe' for SQL Server 2012 (Webedition, 64bit) Grateful to your time and support.
I'm using "C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Update Cache\KB2777772\QFE\setup.exe" to add replication feature, please correct me if I'm wrong.
Thank You.
Regards,
Kalyan
----Learners Curiosity Never Ends----It looks like you are trying to add Replication Components, however, you are using the Cumulative update package 5 setup, which is wrong.
Note that you will not find the setup file for SQL Server on your file system, it will be on your installation media.
To install SQL Server Replication Components, locate your installation media and run Setup.exe. Select the add features to an existing instance option, select your instance, and add replication components.
Brandon Williams (blog |
linkedin) -
Does PB 12.6 support to use other connection method (e.g. OLEDB) MS SQL server 2012 ?
Hi
I checked following page and I understood that PB 12.6 supports native connection for connecting to MS SQL Server 2012.
Latest database native drivers supported by PowerBuilder 12.6
http://wiki.scn.sap.com/wiki/display/SYBPB/Latest+database+native+drivers+supported+by+PowerBuilder+12.6
But there is no info about other connecting methods (e.g. OLEDB).
Does PB 12.6 support to use them ?
And is there a info of it ?
Thanks.
Tsuyoshi YagiHi Tsuyoshi;
1) FYI: OLE-DB and ODBC are examples of "middle-ware" and are not a direct connection to any DBMS vendor!
2) The true native client connection to SS is SNC (SQLServer Native Client). That connection mechanism is supported in PB.
Note: You could also use JDBC or ADO.Net as well from PB. Personally, I always use SNC for the best performance and supported DML functionality.
HTH
Regards ... Chris -
When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
“Unable to connect to the server by using Windows PowerShell remoting”.
Figure 1: Unable to connect to the server by using Windows PowerShell remoting
First of all, we need to verify the configurations as it suggested:
1. The server must be available by using Windows PowerShell remotely.
2. The server must be joined to a domain.
3. The server must be running at least Windows Server 2012 R2.
4. The currently logged on user must be a member of the local Administrators group on the server.
5. Remote Desktop Services connections must be enabled by using Group Policy.
In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
Enable-PSRemoting -Force
Figure 2: Enable PowerShell Remoting
However, if issue persists, we need to check whether it has enough memory to work.
By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
the memory via the PowerShell command below:
Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
Then, you need to restart the server and the issue should be resolved.
You can get more information regarding Remote Troubleshooting by below link:
about_Remote_Troubleshooting
If you need further assistance, welcome to post your questions in the
RDS forum.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.i found another possible reason, this solution worked for me:
http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
I tried to set up powershell remoting on a server and kept getting this error:
Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
ot process the request. It cannot determine the content type of the HTTP response from the destination comput
er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
pic.
After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
many security groups or in my case because of the SidHistory attribute.
The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
If the keys does not exists you can create them, be sure to use the DWORD type.
I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved. -
Issue of Text Qualiffier after upgrading to SQL Server 2014 Standard
Hi,
I'm facing an issue of Text Qualifier after I upgrading my system to SQL Server 2014 Standard Edition (Microsoft SQL Server 2014 - 12.0.2000.8 (X64)
Feb 20 2014 20:04:26
Copyright (c) Microsoft Corporation
Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
I have a csv file with format: Text Qualifier is double pipes ||, Vertical Bar (|) as Column Delimiter and Row Delimiter is CRLF.
For example file:
||Col1|||||Col2||
||ABC|||||XYZ||
This file is working OK in SQL Server 2008 R2 (SP2) but it does not work in SQL Server 2014. It raised error message while running.
Error: An error occurred while skipping data rows.
[SSIS.Pipeline] Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on MediaAgencyGroup returned error code 0xC0202091. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure
code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.
Any suggestion here?
Thanks,Yes
There's a difference in the way text qualifiers are parsed from 2012 onwards
see
http://www.proactivespeaks.com/2012/06/22/my-5-favorite-sql-2012-ssis-features-so-far/
http://blog.concentra.co.uk/2013/06/24/ssis-2012-flat-files-now-greatly-improved-but-are-they-good-enough-yet/
ANyways my preferred way to do this is as below
http://visakhm.blogspot.in/2014/06/ssis-tips-handling-embedded-text.html
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page -
SQL Server 2012 unable to update cumulative update for sql server 2012
Here is the version
Microsoft SQL server 2012 11.02.2100.60X64
Trying to install the update to install sccm2012
Error
There are no SQL server instance or shared feature that can be update on this computer.Hello,
You need CU2 for SQL Server 2012 RTM or later to be able to install SSCM 2012. You can install SP1 for SQL Server 2012 too.
CU2 can be downloaded from the following link:
http://support.microsoft.com/kb/2703275/en-us
When you click on the “Hotfix Download Available” button, make sure you make a click on the “"Show hotfixes for all platforms and languages
(8) " link, then download and install the following file:
SQLServer2012_RTM_CU2_2703275_11_0_2325_x64
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
EHP2 - EHP7 Upgrade Path using SQL Server 2012/Win Server 2012 R2
Hi Guys.
I have question regarging Upgrade Roadmap for a ERP 6 EHP2 system based on NW 7.01 which I would like to Upgrade to ERP6 EHP7 SP7
Source System is
Windows 2012
SQL Server 2008 R2
EHP2 for ERP 6.0 SPS Level 14
Target System
Windows 2012
SQL Server 2012
EHP7 for ERP 6.0 SP 7 based on NW 7.4 SP 9
During Upgrade checks it says I must Upgrade Database first before continue since DB Release is too low for NW 7.4 SP9 as stated in Note
1951491 - Minimal DB system platform requirements for SAP NetWeaver 7.4 SP08
So, at this point I agree i have to update SQL Server to 2012 before next step
Now, my concern is that my Source System does not have the minimum NW SP level (14) to run under SQL Server 2012 which is 26.
Im currently running SAP Kernel 721 EXT Level 401 which is above mininum
According to Note 1651862 - Release planning for Microsoft SQL Server 2012 that would not be possible
Existing systems of SAP products that are out of SAP maintenance can be upgraded to SQL Server 2012 in order to prepare a SAP upgrade, if they match the SAP NetWeaver Support Package requirements defined below.
SAP products prior to SAP NetWeaver 7.0 are not supported at all on SQL Server 2012.
Required minimum SAP Netweaver Support Package Stacks (SPSs) for SQL Server 2012 (SAP ABAP, SAP ABAP+JAVA stacks)
SAP NETWEAVER 7.0 - SPS 26 (SAP BASIS 26, SAP BW 28)
SAP EHP1 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP2 FOR SAP NETWEAVER 7.0 - SPS 11 (SAP BASIS 11, SAP BW 11)
SAP EHP3 FOR SAP NETWEAVER 7.0 - SPS 03 (SAP BASIS 03, SAP BW 03)
SAP NETWEAVER 7.1 - SPS 14 (SAP BASIS SP14)
SAP EHP1 FOR SAP NETWEAVER 7.1 EhP1 - SPS 10(SAP BASIS SP10, SAP BW SP10)
SAP NetWeaver 7.2 - no restriction
SAP NETWEAVER 7.3 - SPS 07 (SAP BASIS 07, SAP BW 07)
SAP EHP1 FOR SAP NETWEAVER 7.3 - SPS 03 (SAP BASIS 03, SAP BW 03)
If your system is running on a SPS lower than the one required above, you have to apply the minimum required SPS before upgrading/migrating to SQL Server 2012.
If you install a NetWeaver product on SQL Server 2012, the required SPS for your product must be applied immediately after the installation - see SAP note 1676665, section I for more information.
But performing the Upgrade would be technically possible? I mean not for productive use but technicaly during that time the Database is Upgrade and during SUM Execution.
According to the note it states if you install a Netweaver Product in SQL Server 2012, SPS must be applied immediately, so is kinda ambigous what SAP is saying.
Best
MartinHi Martin,
For a test scenario, there's no harm in trying it (other than spending a lot of time on it, but hopefully that will prove not to be a waste). Generally, I expect you'll be fine upgrading your DBMS even though you aren't on the required minimum SP yet. The main thing you'll be missing out on is the updates to DBACOCKPIT, but once you do your EhP upgrade (with sps update included), you'll be putting that in place.
So, you could try this on your sandbox system and see if there are any problems. I assume the intent is to start the EhP upgrade as soon as the DBMS upgrade is done, right? In other words, you won't be actually using the system without the required SP except to run the EhP upgrade?
Alternatively, you could do a minimal support pack update, perhaps just a Basis SP only, to the minimum SP needed for your current release, then do the DBMS upgrade, then proceed with the EhP upgrade. This would be the safest procedure, but, as I said, I expect you can probably get away without going to this level without much problem. Again, the idea would be minimizing the time between the start and end of the total project on each system (DEV, QAS, PRD, etc).
Regards,
Matt -
Crystal Reports XI connection problems - after updating to SQL Server 2008
Hello!
We have some ASP.NET 2.0 Applications that call some CR XI report files with parameters to generate PDF Files. After upgrading from SQL Server 2005 to 2008 the apps hang when trying to generate the PDFs. Some research with Fiddler showed that ever time a 401 Error is raised. Calling the reports directly from CR Designer with the same connection values and Parameter shows the appropriate data that means the log-in data iare functioning.
I already tried switching the data source driver from OLE DB to SQL Native - no effect!
Can it be that CR XI does not work with SQL Server 2008? Or is there an update for CR XI and SQL Server 2008?
Because we are in a hurry I hope somebody can solve my problem(s) ...?!
Thanks in advance,
FrankHi Frank,
No CR XI is not supported nor is any version completely at this time. What we've found issues in so far are the Time(7) time is returned as a string value and Stored Procedure Data/time parameter SQL creation. The Time(7) field is an OLE DB driver issue with Microsoft but the Date/time SP issue is our issue and it's currently tracked and escalated. It will be fixed for CR 2008 with SP3 I believe. And I've asked that the same fix be rolled back to CR XI R2 but waiting on the reply from R&D if it can be done.
What you need to do is download the trial version of CR XI R2 ( Release 2 ) and then use your XI Keycode to install it and it will work. Then update to the latest SP 5 Service Pack. XI is past it's end of life support which means there will be no updates or bug fixes any more.
Next, MS SQL Server 2008 does not work with the MDAC version of the Native drivers, you must install the MS SQL Server Client. You'll see the driver name is "MS SQL Server Native client 10". This is the one you need to use.
Another work around is to use ODBC, it seems to resolve all issues, but the client must be installed.
Thank you
Don
Maybe you are looking for
-
Can I drag to the desktop a hyperlink to a specific email in TB?
I want to create a hyperlink in TB so I can place it in a folder, database, or document. When I click on it, I want this hyperlink to open a specific email message in TB. I want to make many of these hyperlinks, each attached to a different email mes
-
Urgent : SAPScript: Main Window
HI Gurus, Can two Main windows be created in a single sapscript with the same text inputs.? If yes, how can we do so? Useful response will be surely rewarded. Thansk in advance
-
Font Arial CE is lost after changing to FM9.0
After updating FramMaker form 7.0 to 9.0 I had to change a polish manual, but the message "Can't find the font Arial CE" (in principal) occurs. In all other programs I can find and use Arial CE. Can pls. somebody tell me how to solve this problem?
-
''Duplicate post, continue here - [https://support.mozilla.com/en-US/questions/806111]'' When I enter any keyword in the adress bar, only the google search enginge opens instead of leading direct to the desired website. In the older FF version it alw
-
How to select .app application package itself on Mac?
Since IOpenFileDialog in CS6 does not support SetNavDlgOpFlags() anymore, I was forced to use AddCustomMenu(). But I could not find a solution or sample to select a Mac OS X application package (.app folder). This Open dialog just shows all the conte