I'm using MS Deploy as it's described here but I'm stuck with dbFullSql string format
Data Source=ISSUETRAK\ISSUETRAK_SERVER;Initial Catalog=Issuetrak;User Id=DOMAIN\Administrator;Password=*****;
and getting the following message
Cannot connect to the database 'Issuetrak'. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_CANNOT_CONNECT_TO_DATABASE.
Object of type 'dbFullSql' and path 'data source=ISSUETRAK\ISSUETRAK_SERVER;initial catalog=Issuetrak;user id=DOMAIN\Administrator' cannot be created.
Failed to connect to server .
Login failed for user 'DOMAIN\Administrator'.
Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.
Failed to connect to server .
Login failed for user 'DOMAIN\Administrator'.
I've managed to move Web Application using WebDeploy without database. And then I did backup SQL database backup on old server and restore on the new one. Hope that helps anyone.
Related
I tried to deploy SSRS report . i created a report on visual studio .. and also i configured report server configuration manager
when i try to deploy report and open this URL
http://localhost/ReportServer
this shows an error
ERROR
"Reporting Services Error
The report server cannot open a connection to the report server database. The log on failed. (rsReportServerDatabaseLogonFailed) Get Online Help
The user name or password is incorrect. (Exception from HRESULT: 0x8007052E)
SQL Server Reporting Services"
whereas when i click reporting services from sql and connect then connected succesfuuly but after when i left click on server name then same error shows as above on sql
This error occurs when Reporting Services (the report server) cannot connect to the "ReportServer" mssql database, It is not a problem in your report but in the server configuration.
To solve it, run the tool "Reporting Services Configuration Manager" in the PC where MSSQL and SSRS are installed, and review everything is ok.
Specially in the Database tab.
The error "The report server cannot open a connection to the report server database. The log on failed" means that:
The database engine that the report server catalog database host is unaccessable.
The Reporting Services service account has insufficient permissions to the access the report server catalog database.
So, to fix the issue, please follow these steps:
Make sure we are able to connect to the database engine from the report server machine.
a) Ping the database engine server.
b) Try to connect to the database engine using SQL Server Mananger Studio(SSMS)(If we have.). Or, create a .UDL file, try to connect the server from this UDL.
Use the Reporting Services Configuration Manager(RSCM) to check the service account. If the report server is on the different server with the database engine, please use a domain account instead of the local account(Built-in account). Make sure the service account has permissions in the database engine.
Final, please check if the report server is configured correctly. We can easily check that by checking if we can open the Report Manager(http:///reports).
Besides, I would suggest you to go through each steps in the RSCM to make sure the configuration is all fine.
For more information, please see:
Configuring a Report Server Installation (Reporting Services in Native Mode): http://msdn.microsoft.com/en-us/library/ms159624.aspx
I made a VM clone of a SQL Server 2012 install. Now on the original install, the SQL Server log is showing login attempts by the clone server.
OLDSERVER was cloned to NEWSERVER, along with SQL 2012 database.
In OLDSERVER logs there are error messages (two per minute) that read:
"Login failed for user 'DOMAIN\NEWSERVER$'. Reason: Could not find a login matching the name provided. [CLIENT: 10.x.x.xxx]. Error: 18456. Severity 14. State: 5."
I am glad the login is failing because I do not want NEWSERVER connecting to the old database. My question is, what process on NEWSERVER is trying to connect to the OLDSERVER SQL database? How do I find it, and shut it off?
I believe I uncovered the problem. The Report Services was trying to connect through the OLDSERVER Report Services database. After changing it to NEWSERVER Report Services, the logs stopped reporting the login error.
I'm new to ETL so I have developed a simple ETL package, and now I'm going to deploy it to a remote server.
I connect to server using SQL Server authentication, so I go to solution explorer and open deployment wizard, in there in destination tab entered my server ip and then it shows me a error message saying
Login failed for user 'MYDOMAIN\MYUSERNAME'. (.Net SqlClient Data Provider)
As I said earlier I want to use SQL Server authentication to connect to my server, where can I change this settings in SSIS ?
Take a look at the link below. I think it should solve your problem.
On the Specify Target SQL Server page, specify the instance of SQL Server to install the packages to and select an authentication mode. If you select SQL Server Authentication, you must provide a user name and a password.
https://technet.microsoft.com/en-us/library/ms141693(v=sql.110).aspx
I have finished my first complete Orchard CMS website, developed locally in SQL Server CE. I want to publish it to Azure, but I am having difficulty with the WebMatrix Migrate function.
I have a SQL Server instance in Azure with an blank Orchard database already there (I want to use the replace option late in the migration to just nuke the existing db). I have added my IP to the server firewall rule.
In WebMatrix 3 I can connect to my Azure database using:
Server: myserver.database.windows.net
Database: orchard-db
Username: admin#myserver
Password: mypassword
I can view the tables in WebMatrix.
When I select my CE sdf file (Orchard.sdf) and click the Migrate button and enter the exact same details I get the following (can provide full stack trace if needed):
We were unable to connect using the connection details provided.
Microsoft.SqlServer.Management.Common.ConnectionFailureException:
Failed to connect to server . ---> System.Data.SqlClient.SqlException:
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: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
---> System.ComponentModel.Win32Exception: The network path was not found
I'm really not sure what the issue is. I have tried various configurations of the details but nothing seems to work. If I connect as my database user (i.e. not a server admin) I get a different error:
The server principal "orchard_user" is not able to access the database "master" under the current security context.
I went and had something to eat, and now I can get to the next step of the migration. When I select replace database I get the following error:
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.SqlServer.Management.Common.ConnectionFailureException: Failed to connect to server . ---> System.Data.SqlClient.SqlException: Login failed for user 'admin'.
EDIT: I have come to the conclusion WebMatrix is not going to migrate my SQL Server CE database to my Azure SQL Server database. I installed SQL Server Express and migrated it to that, when I get home from work I will use the SQL Server Migration Assistant to move it to Azure.
I ended up installing SQL Server Express, using WebMatrix to migrate the SQL Server CE database to that. I then ran the Deploy Database to Microsoft Azure Database Wizard in SSMS to push my database to Azure.
I can't be certain, but it seems that WebMatrix can't migrate CE to Azure. According to Azure doco:
It is recommended that you always use the latest version of Management Studio to remain synchronized with updates to Microsoft Azure and SQL Database. Update SQL Server Management Studio.
I guess WebMatrix is behind or something. Hopefully this helps someone in my situation.
I am in the process of moving all our SharePoint DB's from a SQL 2005 server to a new 2008 server, and after moving the config database, everything seems ok, except when I click on "Timer Job Status" (under Central Admin > Operations > Global Configuration) I receive a "Unable to connect to database. Check database connection information and make sure the database server is running." error.
I get the following entries in the log regarding this:
12/03/2010
13:51:41.80
w3wp.exe
(0x09E0)
0x09AC
Windows SharePoint Services
General
8e2r
Medium
Possible mismatch
between the reported error with code =
0x8107053b and message: "Unable to
connect to database. Check database
connection information and make sure
the database server is running." and
the returned error with code
0x81020024.
12/03/2010
13:51:45.61
OWSTIMER.EXE
(0x0744)
0x0DD8
Windows SharePoint Services
Database
6f8e
Critical
SQL Database
'SP_Test_Config' on SQL Server
instance 'test-server' not found.
Additional error information from SQL
Server is included below. Cannot open
database "SP_Test_Config" requested by
the login. The login failed.
It should be noted that in order to ensure that it was no longer using the config database on the old server, I detached the original SP_Test_Config database in SQL Management Studio.
Obviously there are still references to the old SP_Test_Config database on the old 2005 server. How do I remove these references? Or, barring that, how do I move the config database in such a way that no references to the old 2005 server will remain?
Thank you in advance!
Not really an answer, but what we ended up doing (basically start from scratch using SQL Aliases):
First, create the SQL Server alias. This will make it so if you need to move the databases again in the future, you can just migrate all the databases to the new SQL Server, and change your SQL Server alias to point at that server. This should save you a lot of trouble and heartache in the future.
Run SQL Server Client Configuration Utility at: C:\Windows\System 32\cliconfig.exe.
Under the Alias tab, create a SQL Server Alias for the new SQL Server.
Now, recreate the farm.
Run stsadm -o preparetomove on all content DB's Backup all content DB's and copy to new SQL server
Remove all servers from farm using SharePoint Configuration Wizard
Recreate farm using SharePoint Configuration Wizard with the alias of the SQL Server you created above
Recreate all web apps with temp content DB's
Run stsadm -o deletecontentdb on all temp content databases created in step 4
Run stsadm -o addcontentdb using copied production databases as content database
Troubleshoot ad nauseum