Previously, we had AIF services installed on the same box as the AOS. Something happened with the AIF services and they stopped working using HTTP inbound ports. So, We installed AIF on a new server. What should we do to point to the new AIF server?
Verifying servers:
When I look at the ax32serv.exe.config file, all the endpoint references still point to the old server.
When I refresh from the client configuration utility, I get the error: An error occurred while regenerating WCF configuration: Unable to connect to a Microsoft Dynamics AX WCF service......Metadata contains a reference that cannot be resolved: http://old-server:8101/DynamicsAX/services/RfsCqrsServices
Both ways show that we are still pointing to the old server.
Thank you.
I would have tried the following:
Stop the AOS
Edit ax32serv.exe.config, specify the new server details where required
Start the AOS
Generate full CIL
Related
I have a simple (no authentication yet) Lightswitch VS 2012 app. That on my local computer connects to a mysql database (the database is hosted by my hosting company). All works well.
I then 'publish' this app to my local IIS server, and copy all that to my hosting companies server.
It mostly works, except the WCF service won't work. Upon connecting to the WCF service directly (the .svc file) I get a 'request error'. The stack trace in the Trace.axd is as follows
[Microsoft.LightSwitch.DataService][Application:Error][LightSwitchServiceApplication.vinyldyeData:CreateObjectContext] An exception has occurred: System.ArgumentException: The specified store provider cannot be found in the configuration, or is not valid. ---> System.ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.
at System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName)
at System.Data.EntityClient.EntityConnection.GetFactory(String providerString)
--- End of inner exception stack trace ---
at System.Data.EntityClient.EntityConnection.GetFactory(String providerString)
at System.Data.EntityClient.EntityConnection.ChangeConnectionString(String newConnectionString)
at System.Data.EntityClient.EntityConnection..ctor(String connectionString)
at System.Data.Objects.ObjectContext.CreateEntityConnection(String connectionString)
at LightSwitchApplication.Implementation.vinyldyeDataServiceImplementation.CreateObjectContext()
at Microsoft.LightSwitch.ServerGenerated.Implementation.DataServiceImplementation`1.get_ObjectContext()
It looked as though the hosting company just doesn't have the MySQL Connector in the GAC, so i've added this into the bin folder, still get the same error.
I've looked in the Web.configs, and there is no mention of mysql connector, how does the app know which connector to use?
Have you deployed a Lightswitch app to a host using mysql? if so what files am i missing, or config option.
thanks
Since you've already added the MySQL Connector (I assume 6.4.4) DLLs to the bin folder, refer to this post. Worked for me.
I have a sharepoint server on the DMZ and a SQL2008 server in the local domain.
When I try to get the list of .NETUsers for the Central Administration site from IIS (version 7.5) i get thrown error:26! I have tried all possible combinations in specifying the connection string.
I have also followed all directions on these links to resolve the isssue but it continues to persist.
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
AND
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
Please advise.
Thanks
Firstly, could you check the versions in your question. IIS 6 runs on Windows 2003, but it is not possible to install SharePoint 2010 on Windows 2003.
This is a connection error, there are 2 possibilities:
The call from the SharePoint server is blocked before it arrives at the database
The call is being refused when it arrives at the database
You should start by making a drawing of the route between the Sp server and the database server. make sure to include all firewalls.
Then check the logs to see how far the call got.
You could also try monitoring the network traffic with wireshark to see exactly what is happening.
Going from the Error itself, it turned out be a quite a complicated issue that ended up being resolved after a few days on the phone with Microsoft. The error read "The RPC service is Unavailable". There were issues with the way NetBios and DNS was qualifying the site and server names.
I have been wanting to deploy my SSRS reports to a Test server. However I found that on that server the SSRS service had stopped, and I had to change the setting so that it used a built in Network Service account. After doing that I found I could start the service. However when I key in the ReportService url in my browser, I get the above error message.
One problem that I had when I changed the settings to the Network Service account is that I got the error message:
"A connection could not be established with the information provide. Hit OK to change your connection settings.
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 Privider, error: 40 - Could not open a connection to SQL Server)"
Even so, this did not stop the service from starting.
As a result of all this I still cannot deploy my reports. How do I fix this?
If you are running SSRS 2016, restart the SSRS services:
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
The best way to find the answer is to check the log files.
You can find the log files for report server at below path:
In SQL Server Reporting Services 2016 or earlier: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\LogFiles
In SQL Server Reporting Services 2017: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
Thanks & Regards
Karan
Error 503 Usually comes if the database credentials are wrong , you can test the connection from Reporting Configuration Manager.
Otherwise, Check the Reportserver config file "rsreportserver" at path
C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer
and find the following tags are correct or not.!
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
According to user permissions/properties you can change <AuthenticationTypes> tag.
Restart Following Services
SQL Server Reporting Services (MSSQLSERVER)
SQL Server Reporting Services Web App (MSSQLSERVER)
This error is also generated if you are using a trial version of SSRS and it has expired.
Find <IsWebServiceEnabled>False</IsWebServiceEnabled> and change to
<IsWebServiceEnabled>True</IsWebServiceEnabled> in the rsreportserver
config file.
I was getting this error and tried deleting the URL's from the rsreportserver.config file.
After lots of frustration, I found that the permissions on that file and directory itself did not allow ReportServer user to modify the file. Once I gave the reporting user permission on the file, all was good to remove / update URL's, and returned SSRS back into service.
Try explicitly adding the user permissions to the config file.
Good luck!
In rsreportserver.config, my value was not correct. It was showing up as: http://+:80. Of course, this needs to map to the URL specified in the Report Server Configuration Manager, Web Portal URL (ie the blue URL link that was bringing me to a "not connected" browser screen). It did not, so I got Service Unavailable with a 503 (HTTP error).
The solution: edit the value/address to match the Web Portal URL.
Web Service URL -> URLs: http://MYSERVERNAME:80/Reports
rsreportserver.config -> http://MYSERVERNAME:80/Reports
Once I saved the rsreportserver.config with the edited value to match accordingly (above), I could click on the provided link in the Web Portal section of the Report Server Configuration Manager, and it brought up the SQL Server Reporting Services page. Note: I didn't need to restart anything.
Cheers!
I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.
I am getting an error when I try and upload a import an ssis project onto our server. The server only has integration and reporting services installed as the live sql server is on another server. I log onto the integration service fine but as soon as I try to right click the MSDB folder to import a package I get the error listed at the end of this question. I have added my local user account as an administrator on the server where the Integration Service is installed and I have added the administrators group to the security permissions for MsDtsServer in component services. Any help with this would be appreciated.
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
ADDITIONAL INFORMATION:
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
BUTTONS:
OK
I had this problem recently. It was a little tricky to figure out.
Here is a nice link from MSDN on how to hack, err, I mean fix it.
Configuring the Integration Services Service
"To manage packages that are stored in a named instance or a remote instance of the Database Engine, or in multiple instances of the Database Engine, you have to modify the configuration file." - MSDN
Thanks Microsoft??
To be more specific, you need to edit this file on your server:
C:\Program Files\Microsoft SQL Server\90\DTS\Binn\ MsDtsSrvr.ini.xml
Change:
<ServerName>.</ServerName>
to
<ServerName>ServerName\InstanceName</ServerName>
Save. and reboot.
Is your server set up to accept remote sql connections? Maybe check your firewall on the server to check that all the SSIS ports are allowed through, and also check in the SQL Surface Area Configuration tool to make sure all the services are set up to allow remote connections.