SQL Database Login failure

I'm getting a SQL database login failure on one customer after many successful installations at other customers. My app uses OLE DB (ADO) database type with the SQLOLEDB provider to access the database. I create the table logon info structure internally in my app and use that to connect the Crystal Report for.Net framework to the database. I've verified that the server name is correct and the database allows access from SQL Management Studio and from the rest of my app, which uses VB SQL connection objects. But on this one customer I get a "Database Login" prompt when the Crystal Report is run. The prompt shows the correct user name and password. When I hit "Login" the login fails (as it failed internally leading to the dialog being shown in the first place).
Anyone have any idea on what's going on here? Any idea on where else to look? I suspect some software the customer is running is interfering somehow with Crystal Reports. But I don't have any idea of what to check for. Any help will be appreciated.
Jon Webb
PEP Systems, Inc.

Some of the more common causes for this are:
1. Firewalls - If you have a firewall between the database server and your computer
2. Different SubNets. If your database server is on a different sub-net than the computer you are trying to connnect from - then it might not be able to see it / resolve the name. To verify this, trying pinging the database computer by machine name (e.g. ping myDBServer). This can also be caused by the computer not being able to see the DNS server, and so not able to resolve the DB server machine name.
3. Wrong DB driver version. Sometimes if you are trying to connect to a newer version of SQL server using older drivers - it won't work. Verify what version of the SQL server drivers are being used.
4. MDAC is not installed. To connect via ODBC you sometimes need MDAC installed. You can check the version using the info in this kbase http://support.microsoft.com/kb/301202
Shawn

Similar Messages

SQL database login for 'SharePoint_Config_2010' on instance 'DB server' failed. Additional error information from SQL Server is included below.

we formatted Database server and restored all the databases from the backup. but the sharepoint site is giving below error when i access the home page.
we have 3 application servers in that two are working fine, but only one server getting the below error.
SQL database login for 'SharePoint_Config_2010' on instance 'db server' failed. Additional error information from SQL Server is included below.
Login failed for user 'domain\user'.
could you help what is the issue?

Hi,
According to your post, my understanding is that you failed to access sharepoint site with one application server.
It was due to the MOM/SCOM Agent that has a SharePoint management pack installed, the agents Windows Service runs as ‘Local System’ and thus causes this.
The workaround is to either kill the SCOM agent service, or set it to run as a dedicated service account.
In addtion, I recommend to add the logon account of the SharePoint Timer service as a user of the SharePoint_Config database. Give role membership to the account db_owner.
You also need to add the SharePoint accounts back into sql server.
There are some similar articles for you to take a look at:
http://blog.blksthl.com/2012/04/26/login-for-sharepoint_config-login-failed-for-user-domaincomputername-scom-agent/
http://msdn.microsoft.com/en-us/library/jj551781(v=nav.70).aspx
http://sharepoint.stackexchange.com/questions/51623/moved-sql-databases-for-sharepoint-2010-and-now-have-a-3351-error
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Event 3351, SQL database login for 'DB_Config' on instance failed. Additional error information from SQL server is mentioned below. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

category-database
event id-3351
source-sharepoint foundation
SQL database login for 'DB_Config' on instance 'DB\instance' failed. Additional error information from SQL Server is included below:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.
I have been getting this error every hour on only 1 application server of the 2.
My farm consists of 2 app servers, 2 wfes & 2 sql nodes.
My public site is working fine. Authentication is NTLM.
SharePoint VSS Writer is disabled.None of my appPool accounts are running under local system.
I have read many forums/blogs, but couldnt find a solution for this.
Any help would be appreciated!

Hi,
As I understand, you found event id 3351 in event log. Please collect more information as below：
Check if the error also occurs on other servers in your farm.
Check if backup job is scheduled at the time when the event id occurs.
Please run Config Wizard or psconfig.exe -cmd secureresources on all servers and test the issue again.
Regards,
Rebecca Tu
TechNet Community Support

Intermittant (not constant) SQL database ShareWebDb login failed events 3760 and 2424

My Sharepoint 3.0 services that were bundled with SBS 2008 appear to be working fine. Companyweb, etc, all work w/o issue, so I don't want to take violent action, but these errors seem to be accellerating so I would love to know if there is a known
solution.
I typically receive the following (these are in reverse time order, latest at the top, just as they appear in the event log):
Error Event ID: 3760 SQL Database 'ShareWebDb' on SQL Server instance 'np:\\.\pipe\MSSQL$Microsoft##SSEE\sql\query' not found. Additional error information from SQL Server is included below. Cannot open database "ShareWebDb" requested
by the login. The login failed. Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.
one second earlier:Error Event ID: 2424 The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again. Context: Application 'Search', Catalog 'index file
on the search server Search'
Information Event ID: 18456 No description, here is the Details:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider
Name="MSSQL$MICROSOFT##SSEE" />
<EventID Qualifiers="49152">18456</EventID>
<Level>0</Level>
<Task>4</Task>
<Keywords>0x90000000000000</Keywords>
<TimeCreated
SystemTime="2010-11-12T18:35:06.000Z" />
<EventRecordID>491461</EventRecordID>
<Channel>Application</Channel>
<Computer>myserver.mydomain.local</Computer>
<Security
UserID="S-1-5-20" />
</System>
<EventData>
<Data>NT AUTHORITY\NETWORK SERVICE</Data>
<Data>[CLIENT: <named pipe>]</Data>
<Binary>184800000E000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary>
</EventData>
</Event>
Two seconds earlier
Information Event ID 17137 No description, here is the Details:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider
Name="MSSQL$MICROSOFT##SSEE" />
<EventID Qualifiers="16384">17137</EventID>
<Level>4</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated
SystemTime="2010-11-12T18:35:04.000Z" />
<EventRecordID>491460</EventRecordID>
<Channel>Application</Channel>
<Computer>mysever.mydomain.local</Computer>
<Security
UserID="S-1-5-20" />
</System>
<EventData>
<Data>ShareWebDb</Data>
<Binary>F14200000A000000170000005000450054003300310030005C004D004900430052004F0053004F00460054002300230053005300450045000000070000006D00610073007400650072000000</Binary>
</EventData>
</Event>
I get more 3760 errors than 2424's. However, the
2424's do seem to usually correspond to a 3760 18456 17137 occurance and the
3760 are always preceeded by 18456 17137. I was getting one or two sets a day, lately that has increased to 5 or 10.
I've done a lot of
web research on Sharepoint Errors 3760 and
2424 and I see a number of people are experiencing the the same issue. Most of what I've come across for solutions do not apply, since errors are intermittent, not chronic and my public remote URL has already been added
to BackConnectionHostNames as per:
http://blogs.technet.com/b/sbs/archive/2009/08/05/sharepoint-services-3-search-event-errors-after-an-sbs-2008-update-rollup.aspx
I installed the SQL Server Management Studio Express so I could try to track down the permissions on this database. I see the SQL server instance, MYSERVER\Microsoft##ssee, and it shows as running, but when I try to connect to it I get the following
error: "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote
connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)" I'm assuming that is because I don't have access permission for that internal database.
I don't see any errors in the event log related to failed logins or any errors at all from the SQL server, but there are the time matching informational entries right before the error events and lots of other 17137's and 2803's from MSSQL$Microsoft##ssee

Thank you Kevin, that does seem to match my symptoms and I have made the change suggested. Just incase that page becomes unreachable by others, here is the part of the page that applies to this:
Issue:
=========
Receive event error 3760 and 6398 on SBS 2008
Cause:
==========
Issue was caused by incorrect Auto Close option for ShareWebDb database
Solution:
==========
1. On the SBS 2008 server, click Start -> All Programs -> Microsoft SQL Server 2005, right click SQL Server Management Studio Express and choose run as administrator.
NOTE: You must run it as administrator to perform steps below.
2. In the Server Name box, type \\.\pipe\MSSQL$Microsoft##SSEE\sql\query, click connect.
3. Expand Database node and right click the ShareWebDb then choose properties.
4. Click Options in the left pane, in the right pane, please check whether the Auto Close option is set to True, if so, please change it to False.

Can't connect to SQL Database using new login

I can connect to Azure SQL Database using the admin ID created when I set up the Azure account. Now I want to set up a different login that has only regular read/write privileges. I have followed the instructions on several web posts, to create
a login at the server level, then create a user at the database level from the login. When I try to connect, though, the connection fails. I get an error message, and a GUID that I am supposed to supply to MS tech support, except that all I have
is a standard Azure subscription, which does not include tech support.
Here is what I have done so far:
Logging in to the server with the admin account with SQL Mgmt Studio, I go to the master database on my Azure server, and create the login:
CREATE LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
This appears to work (password supplied is a "strong" password), or at least it doesn't show any error response.
Then, connecting to the production database in Azure, I set up a user and set permissions as follow:
CREATE USER clouduser1 FROM LOGIN clouduser@gxw8x04nlb;
EXEC sp_addrolemember 'db_datareader', 'clouduser1'
EXEC sp_addrolemember 'db_datawriter', 'clouduser1'
When I attempt to connect to Azure using the new login, however, I get an error message (from SQL Mgmt Studio as well as from MS Access). I am using the SQL Server Native Client 10.0.
The message is:
Connection failed:
SQLState '28000'
SQL Server Error 18456
[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'clouduser'.
Connection failed:
SQLState: '01000'
SQL Server Error: 40608
[Microsoft][SQL Server Native Client 10.0][SQL Server]This session has been assigned a tracing ID of
'271851d5-8e94-497c-a332-d9d40682bb7a'. Provide this tracing ID to customer support when you need assistance.
Is there some missing step I need to do, to permit the login to see the database? I have looked for such in the various discussions about connection problems, but have not been able to find such a thing. Or extend more permissions to the new
user? Or specify a default user ID for a given login ? (as they do not have the same names, in the examples I have seen). I tried making the user ID the same as the login (w/o the server name), but that didn't seem to help, either.
I have done numerous web searches, and tried about every variation of login or user ID, password, etc. that I can think of, and all of them encounter the same error. It's got to be something very simple - clearly Azure supports more than one login
per database. But's that's all I have at the moment. That login connects just fine, but others won't, using the same PC, middleware, IP address, etc.
Any help would be much appreciated -
Thanks,
Doug

Olaf -
I noticed that, but all of the examples I have seen have Users named slightly differently from the Logins. I did try logging in with the Login name instead. No good. I tried making the Login and the User name the same (clouduser). Also
no good - same symptoms.
I think the problem is that the initial creation of the Login needs to be done WITHOUT the server name on the end.
Logged in to the master DB, I tried: Create LOGIN clouduser@gxw8x04nlb with PASSWORD = 'xoxoxoxo';
That didn't give me an error message, but I think it created a LOGIN of 'clouduser@gxw8x04nlb'. When
referenced from the outside world, I would need to specify 'clouduser@gxw8x04nlb@gxw8x04nlb'.
I tried deleting the logins, and then creating the login 'clouduser' in the Master DB. Then in
the application DB, I created User clouduser from LOGIN clouduser, and then assigned a role. That seems to work!
In my connection string, File DSN, etc. I still need to supply the login as 'clouduser@gxw8x04nlb'.
But when I am logged in to the server, and working in the Master DB or the application DB, I just refer to the Login as 'clouduser'.
Seems a little more complicated than it really should be, but at least I now have something that works.
Doug
Doug Hudson

After creating a contained database, getting a login failure error while trying to connect to it.

After creating a contained database and a user with passowrd under the same database, I tried connecting to the contained database. I entered the server name, login credentials and went to the connection properties tab to select the contained database using
<browse server> option under "connect to database". Here I get the login failure error.
TITLE: Browse Server for Database
Failed to connect to server <servername>\<login>. (Microsoft.SqlServer.ConnectionInfo)
But when I manually enter the Database name instead of selecting from the <browse server> option the connection gets through.
Is this a Bug ? Has anyone else faced this error?

Hello,
Is this a Bug ? Has anyone else faced this error?
It's not a bug, it's working as intended. Contained users don't have instance level permissions and cannot "login" to the instance (which is what the "browse" button is attempting). In order for it to work, the database name must be in the connection string
(which with the browse button, it will not be).
Welcome to contained users, they aren't for everyone.
Sean Gallardy | Blog | Microsoft Certified Master

SQL Server 2012 syspolicy_purge_history job causes cross-instance login failures w. EraseSystemHealthPhantomRecords

I have unique service accounts set up for multiple instances on the same SQL Server 2012.
When step 3 of the inbuilt syspolicy_purge_history job(Erase Phantom System Health Records) runs, it appears to attempt to run against every instance on the server despite being passed the instance path!
The SQLServer's powershell script call:
if ('$(ESCAPE_SQUOTE(INST))' -eq 'MSSQLSERVER') {$a = '\DEFAULT'} ELSE {$a = ''};
(Get-Item SQLSERVER:\SQLPolicy\$(ESCAPE_NONE(SRVR))$a).EraseSystemHealthPhantomRecords()
so with instances SERVER\X this runs as...
(Get-Item SQLSERVER:\SQLPolicy\SERVER\X).EraseSystemHealthPhantomRecords()
SERVER\X's job will run and I will see login failures in the error logs of SERVER\Y and SERVER\Z for the service account set up for instance X.
It seems Microsoft's only 'accepted solution' to this problem is for me to compromise my security by escalating the access of these service accounts?
Has anyone else run into and corrected this failure?

Hi Atombath,
When you install multiple instances on one Server, and the SQL Server’s powershell scripts are the same in inbuilt syspolicy_purge_history job steps. However, when you start PowerShell by right clicking
syspolicy_purge_history job, you will find it will point to their own instance. I do a test in my SQL Server 2012,
it will not across instance to collect the error logs. So I recommend you use its original powershell scripts for the syspolicy_purge_history job.
Sometimes, if you run the syspolicy_purge_history job on a clustered instance, the syspolicy_purge_history SQL Server Agent job may fail due to using the computer node name instead of the virtual server name. For more information, see:
http://support.microsoft.com/kb/955726/en-us
In addition, you can use different service account for your multiple SQL Server instances on the same Server. And make sure the accounts that you created get added to the sysadmin fixed server role, the accounts are also set in the three Agent roles (SqlAgentUserRole,
SqlAgentReaderRole, and SqlAgentOperatorRole).
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Essbase Error(1021001) Failed to Establish Connection With SQL Database...?

Hi there!
I am very new in Essbase and I am receiving the error message quoted below while trying to load data in a Cube. Weird thing is that we have checked all connections already and they are working correctly, however this process is still failing.
If someone can give us an idea to troubleshoot it, that would be really appreciated.
Thanks very much in advance for any help and regards!
MAXL> deploy data from model 'Production_GL_Cube_SchemaModel' in cube schema '\Production_GL\Cube_Schemas\Production_GL_Cube_Schema' login AdminUserAccount identified by MyPassword on host 'ServerName.MyCompany.com' to application 'ORA_HFM' database 'GL' overwrite values using connection 'ServerName' keep all errors on error ignore dataload write 'E:\Logs\DataLoad_Error_2013.04.19.16.23.00.txt';
BPM Connect Status: Success
Failed to deploy Essbase cube. Caused by: Failed to load data into database: GL. Caused by: Cannot get async process
state. Essbase Error(1021001): Failed to Establish Connection With SQL Database Server. See log for more information
BPM maxl deployment ...failure.

Hi Celvin,
Thanks for your reply and my apologies for not coming back before on this issue.
For the benefit of other readers, after hours struggling with the issue, we focused our attention in the following portion of the ORA_HFM.log file:
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/54996/Info(1013157)
Received Command [Import] from user [Service_Acct@Native Directory] using [GL.rul] with data file [SQL]
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021041)
Connection String is [DRIVER={DataDirect 6.1 Oracle Wire Protocol};Host=MyEssbaseServer01.MyCompany.com;Port=1521;SID=PRODUCTION;UID=...;PWD=...;ArraySize=1000000;]
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021006)
SELECT Statement [SELECT cp_127."ACCT" AS "Accounts_CHILD",
         cp_127."PERIOD_MEMBER" AS "Period_CHILD",
         cp_127."PERIOD_YEAR" AS "Years_CHILD",
         'INPUT' AS "View_CHILD",
         cp_127."ENTITY" AS "Entity_CHILD",
         cp_127."PRODUCT_LINE" AS "Custom1_Product_CHILD",
         cp_127."Function" AS "Custom4_Function_CHILD",
         cp_127."B_U" AS "Business_Unit_ORACLEBUSINESS",
         cp_127."ORACLEFUNCTION" AS "Oracle_Function_CHILD",
         cp_127."LEGALENTITY" AS "Oracle_Entity_CHILD",
         'P' || cp_127."PRODUCTLINE" AS "Oracle_Product_CHILD",
         'A'[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021043)
Connection has been established
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021044)
Starting to execute query
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021013)
ODBC Layer Error: [S1000] ==> [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-04063: view "REP_ESSBASE.VW_GL_BALANCES" has errors]
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Info(1021014)
ODBC Layer Error: Native Error code [4063]
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Error(1021001)
Failed to Establish Connection With SQL Database Server. See log for more information
[Sat Apr 20 11:48:34 2013]Local/ORA_HFM/GL/Service_Acct@Native Directory/8964/Error(1003050)
Data Load Transaction Aborted With Error [1021001]
Then we concentrated in the following error message: *ODBC Layer Error: [S1000] ==> [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-04063: view "REP_ESSBASE.VW_GL_BALANCES" has errors]*
So, we checked the database and noticed the schema and their views were damaged and -due to this- they lost all their properties (like data types, for example). So, we had to recompile all of them in order to avoid any loss of data. This was done in TOAD, as per the following info: https://support.quest.com/SolutionDetail.aspx?id=SOL66821
Finally, once all the views on this schema were rebuilt and fixed, we were able to deploy the Cube again.
Hope this help in the future. Cheers!!

Design a job for Login failure alert

HI,
I need a query to get Login failure alert for both windows login and SQL login account. Also i need track to which database the Login user is connecting while he is getting Login failure error. I need to to schedule this as a job.

To check what database was being used when the login failed, you will need to use default trace as mentioned in the link below:-
http://www.eraofdata.com/the-sql-server-default-trace/
or simply run the query below:-
SELECT TE.name AS [EventName] ,
v.subclass_name ,
T.DatabaseName ,
t.DatabaseID ,
t.NTDomainName ,
t.ApplicationName ,
t.LoginName ,
t.SPID ,
t.StartTime ,
t.SessionLoginName
FROM sys.fn_trace_gettable(CONVERT(VARCHAR(150), (
SELECT TOP 1
f.[value]
FROM sys.fn_trace_getinfo(NULL) f
WHERE f.property = 2)), DEFAULT) T
JOIN sys.trace_events TE
ON T.EventClass = TE.trace_event_id
JOIN sys.trace_subclass_values v
ON v.trace_event_id = TE.trace_event_id
AND v.subclass_value = t.EventSubClass
WHERE te.name IN ( 'Audit Login Failed' )
order by t.StartTime desc
The only other way would be to use Auditing, Server Side Trace or Triggers if you want to maintain history of these.
Reference:
http://sqlrows.blogspot.in/2011/10/note-to-self.html
Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana

ERROR – SQL Server Login Failed, Error 11001

We have an application that uses MSDE as its ‘Back-end’.
It has been working fine for years. We have however had to recently re-build the Operating System on our own Server that it was running on.
Original O/S Environment
We used Windows Server 2008 r2, using
Hyper-V to run Windows Server 2003 so that we can use
MSDE to run our application.
We do not want to change to later versions of SQL Server Express as they no-longer support Replication.
NEW O/S Environment
When we re-built the Server we went for Windows Server 2008 r2, using
Hyper-V to run Windows 7 Enterprise so that we can use
MSDE to run our application.
We have used this setup many times before and know that MSDE runs quite happily under Windows 7.
Servers have been renamed
The real Windows Server 2008 r2 machine used to be called FILESERVER.
It is now called FILE-SERVER.
The virtual machine running our application was originally called GEMSERVER.
It is now called GEM-SERVER.
What’s happening on the Server
The application is running fine. We can access the underlying MDSE Database with SQL Server 2005 Management Studio Express without problem.
We can build a test ODBC Data Source and connect to the ‘SQL Server’ Database, again without problems.
What’s happening on the Client PC
The application does not connect. I get:
     An error occurred while connecting.
     [DBNETLIB]ConnectionOpen (Connect())SQL Server does not exist
     or access denied.
When I build a ODBC Data Source to test the Connection I get:
Microsoft SQL Server Login
Connection failed:
     SQLState: '01000'
     SQL Server Error: 11001
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
     (Connect()).
     Connection failed:
     SQLState: '08001'
     SQL Server Error: 6
     [Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified SQL
     server not found
I can Ping GEM-SERVER from the Client PC without problems.
I have disabled Firewalls an Anti-Virus Software on both the GEM-SERVER and the Client PC – to no avail.
I’ve tried connecting with:
Named Pipes,
TCP/IP,
IP Address of GEM-SERVER – 192.168.16.122,
Using Specific Port 1433 in connection.
NONE of it worked. L
ANYBODY any ideas what to try next?

Here's the solution that we came up with to our own problem:
This problem was actually caused by a bug in our own Application.
For some reason when we restored our MDSE Database the correct SQL Server Access Protocols were not setup correctly. (It is designed to handle these setup issues for us and has done so previously.)
We still have to determine why it happened and rectify the problem within our Software.
However to correct the problem with our own 'Server' we had to manually:
Run netsvrcn.exe using command prompt as an Administrator on the ‘Server’ running the MSDE Database,
Enable TCP and NAMED PIPES protocol
Restart SQL Server instance
Exclude the ports SQL Server normally listens on, from the firewall using ‘Windows Firewall Advanced Security’ for both in-bound and out-bound rules:
1433 TCP port
1434 UDP port
We then tested the ODBC connection from client machine and found that it worked fine, as indeed did our application.
However we still have a residual problem.
For we cannot connect to our Server called GEM-SERVER using GEM-SERVER\GEMSQLSRVR we have had to use 192.168.16.122\GEMSQLSRVR.
We are not sure why. We obviously wish to use the machine’s name rather than its IP Address, as its IP Address is dynamically assigned by a DHCP server so may change in future.
Do I need to raise this remaining problem as a separate issue?

Missing DataBase Login information for deployed VS2008 w/Crystal Report

I'm creating a Windows Form application using VS2008 Pro and the basic Crystal Reports (included).
I've successfully added a crystalreportviewer control and a crystal report (.rpt) to my form. I've written the following code in the code behind to programmatically load/bind the report to the viewer. Everything works fine on my development machine (or any machine that has Visual Studio installed). Where I'm encountering problems is when I deploy the application to a machine that does not have VS installed (I have downloaded and installed the "Crystal Reports Basic for Visual Studio 2008 Redistributable Package" for the appropriate processor type on this non development machine) that I'm getting an error . It prompts for "DataBase Login". The ServerName, LoginID and Password are all there, but the "DataBase" field is empty and disable for user input.
Why is the DataBase information missing? How can I solve this problem?
(On a side note, I vaguely remember a property for enabling/disabling the prompting of the database login. I can't remember where this was again to double check if that is the culprit. But I'm pretty sure that I did mark it as to not prompt, since it's supplied in the code behind. Plus it doesn't prompt on the development machines. Only on the non-development machines).
Any help is greatly appreciated! Thanks.
The code executed in the PageLoad event of the form.
this.crystalReportViewer1.RefreshReport();
 ReportDocument reportDocument = new ReportDocument();
 #region Load Parameters
 ParameterFields paramFields = new ParameterFields();
 for (int i = 0; i < _parameterName.Length; i++)
 {
 ParameterField paramField = new ParameterField();
 paramField.ParameterFieldName = _parameterName;
 ParameterDiscreteValue discreteVal = new ParameterDiscreteValue();
 discreteVal.Value = _parameterValues;
 paramField.CurrentValues.Add(discreteVal);
 paramFields.Add(paramField);
 }
 crystalReportViewer1.ParameterFieldInfo = paramFields;
 #endregion
 #region Load Report
 string reportUrl = "";
 string exePath = Application.ExecutablePath.ToString();
 exePath = exePath.Remove(exePath.Length - 18, 18);
 exePath += _reportName + ".rpt";
 reportUrl = exePath;
 reportDocument.Load(reportUrl);
 #endregion
 reportDocument.SetDatabaseLogon("myUserName", "myPassword", "myServer", "myDataBase");
 crystalReportViewer1.ReportSource = reportDocument;

Edited by: mtech8 on Jan 9, 2010 3:03 PM. Corrected formatting issues to make post readable.

HI. Ludek,
Thanks for the tips. I tried both, but the problem presists.
On a side note, I did get my hands on yet another "non-development machine". This one ran with Window's Vista appeared to work (even with my original code).
The "non-development machines" that I've tested on are Windows 7 and Window XP machines. On these machines, when I commented out the reportDocument.SetDatabaseLogon line, when I try to load the report, it still prompts for the Database Logon information, however, it also has the "Database name" empty and disabled.
Since it worked on a non-development machine with Win Vista. I don't think there is a problem with references or the Crystal runtime packages.
As far as permission for the report to contact the database, I'm guessing there isn't a problem there either because the application does successfully connect to the database.
I'm connecting to a SQL2005 database and using the SQL Native connection.
On a side note: as for the enabling prompting, I just remembered that it was an option available when using Crystal Reports with a web project. Thus I couldn't find it here with a Window's Form project.

Advise on SQL database process

Dear all,
We have build our own product CMS platform configuration which is running on SQL server and CMS web site link to it.
We will lauch our product soon but need to identify the correct hosting plan for not having any further issue.
For exemple for now all is hosted in our company azure account with a Standard Basic 5 DTU's.
When we go in production we can expect some connection and big amount of data on our database.
My question are as follow :
- Does using a single database storage for my potential Customers would be enough ?
- How should I plan backup efficiently ?
- Should I plan a safety replication process somewhere in azure or duplicate the storage in order to switch in case of lack of place ?
My concern is to avoid my database beeing full while customers increase
Thanks for your advise and help
regards
serge

Hi Solatys,
- If I select by default STANDARD Azure database, which size, DTU, etc should I select ?
For this question, you may reference the below link. You can scale your Azure database performance based on the real-time requirement.
Azure
SQL Database introduces new near real-time performance metrics
- If for instance the initial URL of the web portal connected to SQL server1 has a trouble, how can I switch users transparently to a second replicated server in order that user will notify anything ?
Azure SQL Database has a built-in high availability subsystem that protects your database from failures of individual servers and devices in a datacenter. Azure SQL
Database maintains multiple copies of all data in different physical nodes located across fully independent physical sub-systems to mitigate outages due to failures of individual server components, such as hard drives, network interface adapters, or even entire
servers. At any one time, three database replicas are running—one primary replica and two or more
secondary replicas. Data is written to the primary and one secondary replica using a quorum based commit scheme before the transaction is considered committed.
If the hardware fails on the primary replica, Azure SQL Database detects the failure and fails over to the secondary replica. In case of a physical loss of a replica, a new replica is automatically created.
So there are always at minimum two physical, transactionally consistent copies of your data in the datacenter.
Azure SQL Database Business Continuity
- IF I select the Maximum size of the database, what will happen in case it will be nearly full and need to provide more space ?
Insert and update transactions that exceed the upper limit will be rejected because the database will be in read-only mode. The maximum size has been gained from 50GB to 500GB as of now, you may have no concern about it. You can
set a monitoring alertto
notify the storage utilization and CPU percentage etc.
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

Crystal Report Print Preview presenting users with Database Login

Issue
A user amended a crystal report form, on doing so has now made that Form unavailable to the majority of users to Print or Preview this is in 8.8 PL10. All other users on Previewing are presented with a window Database Login, but this only presents the server name, Database name is blank and greyed out and then there is only Login ID and Password available. If you enter in the database password a message appears stating failed login.
We have access to the SAP server and logged in and get the same message! but on the users machine who amended the Form they can print? any suggestions greatly appreciated

Hi Roger,
The problem sounds similar to what I've had recently, it was resolved by changing the database connection type to SAP Business One in Crystal Reports 2008, I can confirm that using OLE DB or other will still cause the login issue on other machines off the SQL server, the SAP Business one connection solves the issue.
I was fighting with this for hours, hope this helps you all.

Windows 7 clients suddenly unable to connect to SQL database

Our environment in a nutshell:
Server1: Small Business Server 2003 R2 (Active Directory domain, it is the sole domain controller [DC])
Server2: Dedicated to SQL Server 2005 and the SAP Business One database
Server3: Windows Server 2003 R2 Standard Terminal Server. This provides user sessions that are the equivalent of Windows XP SP3.
Two Windows 7 workstations: 1x 64-bit, 1x 32-bit. Both are domain joined.
All above computers on a gigabit LAN.
Client product is SAP Business One 2007 A (8.00.181) SP:00 PL:49
SQL Native Client is 9.00.5000.00
SQL Server is mixed-mode authentication, however all users use trusted Windows connections. All users with access to the product are members of an "SAP Users" domain security group.
Normal operation is:
Local Win7 workstations have client installed and connect over the LAN to the SQL Server instance on Server2
Remote users log on to the Server3 Terminal Server, fire up sessions and connect to the SQL Server instance
Up to and including Thursday, March 12 everything was working fine for all users. As of Friday, March 13 the Terminal Server users/sessions are still working perfectly but the Windows 7 workstations can no longer connect to the SQL Server instance with trusted connections. They are still able to connect if they switch to a SQL Server logon and use the "sa" user account and its password.
Also, the users normally using the Win7 workstations can log on to the Terminal Server with their usual domain accounts, and run SAP from there, which works perfectly.
The error the Windows 7 users are seeing:
Connection failed:
SQL State: 28000
SQL Server Error: 18452
[Microsoft][SQL Native Client][SQL Server]Login failed for user ". The user is not associated with a trusted SQL Server connection.
Prior to each logon attempt above, the Server2 SQL Server machine logs another event to its Application Event Log:
SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: xx.xx.xx.xx]
Source: SQL Server instance, event 17806. From SQL Server log, Severity 20, State 2
What I've tried so far:
All servers have been restarted in correct order
Running the client in Windows XP SP3 compatibility mode. No difference
Running the client as Administrator. No difference
Upgrading to SQL Server Native Client 11.0 via:
Uninstall B1 client
Uninstall v9.00 Native Client
Install v11.00 Native Client
Install B1 client
Net effect is no difference
Googling the event IDs that are being logged seems to point to:
Expired domain account. Manually checked that the 2 users accounts are not expired and they belong to the "SAP Users" group. Furthermore, the domain accounts are still working when used in Terminal Server sessions.
Problem with Service Primary Names (SPNs). This seems to be Active Directory-related. Again, the domain accounts normally used on the Win7 workstations work fine on the Terminal Server so I'm inclined to think AD is OK
Other information that may be useful:
No Windows updates applied between March 12 and 13 on either Win7 workstation
Both Win7 workstations running Microsoft Security Essentials and the native Windows 7 firewall
All servers running Trend Worry Free Business Security suite
Sorry about the length of the post but hopefully it will reduce wild goose chases. Any troubleshooting ideas greatly appreciated.

Problem found!
It turns out it was some sort of subtle problem with Trend antivirus running on the servers.
On all 3 servers there are 3 main protection components that are enabled by default:
Antivirus/Anti-spyware
Web Reputation
URL Filtering
What I did was to turn off all 3 components for all the servers. With Trend this can be done from the central management console. SAP then worked on one of the Win7 clients using Trusted Connection (i.e. Windows Authentication).
Then I turned the Trend components back on, on all servers, one at a time (to try to find which component was the culprit). Here’s the funny part: I turned all 3 back on, and SAP still works on the Win7 client using Windows Authentication! I even restarted it to make sure that state of affairs persists across a restart, and it’s still OK.
It's worth noting the problem was not solved shortly after it appeared by restarting all 3 servers. There was even a scheduled installation of Windows updates a couple of hours ago, which restarted all 3 servers again, and the problem still persisted. It was not fixed until the Trend components were globally disabled (on all 3 servers), then re-enabled.
Trend WBFS is version 9.0, pre SP1.

Can No Longer Connect to Azure SQL Databases

As of this morning, I am no longer to connect to any of my Azure SQL databases by any (apparent) means. I checked the configuration in the azure portal and my IP address is listed as an allowed IP, however:
I am unable to connect via SQL Server Management Studio
My request times out when attempting to visit https://{server_name}.database.windows.net
What might have caused this?

Hi ,
Thanks for posting here.
To resolve the issue you can try the following steps (in that order):
                Check the application’s connection string to make sure that it is correctly configured. For example, make sure that the connection string specifies the correct port
(1433) and the fully qualified server name.
Note You can follow these steps to obtain the connection string from the Azure Management Portal:
                      Log on to the
Azure Management Portal.
                      In the left navigation pane, click
SQL Databases.
                      Select your Azure SQL Database server.
                      Click
Dashboard.
                      On the right side, go to the
quick glance section, and then click Show connection strings.
                Make sure that TCP IP is enabled as a client protocol on the application server. For more information on how to do this, see
Configure client protocols. On application servers where you do not have SQL Server tools installed, you can check this by running cliconfg.exe (SQL Server Client Network Utility).
                Test the connectivity between the application server and the Azure SQL database by using a UDL file, ping, and telnet. For more information about how to do this,
see
Azure SQL Database connectivity troubleshooting guide and
Troubleshooting SQL Server connectivity issues.
Note As a troubleshooting step, you can also try to test the connectivity on a different client computer.
                Try increasing the connection
timeout. Microsoft recommends using a connection timeout of at least 30 seconds.
                As a best practice ensure retry logic is in place. For more information about the retry logic, see
Azure SQL Database best practices to prevent request denials or connection termination.
              If the previous steps do not resolve your problem, follow these steps to collect more data and contact support:
                  If your application is a cloud service, enable the logging. This step returns a UTC time stamp of the failure. Additionally, SQL Azure returns the tracing
ID.
Microsoft Customer Support Services can use this information.
                  For more information about how to enable the logging, see
how to enable diagnostic logging for Azure Web sites and Developing SQL Database Applications section in
Azure SQL Database Development Considerations.
Please write back with the exact Error message/ Error Code if this doesn't help.
Regards,
Shirisha Paderu.

SQL Database Login failure

Similar Messages

Maybe you are looking for