I have a vb.net application that communicates with Exchange 2000 & 2003 using WebDAV, but it does not work with Exchange 2007 SP2
Test Environment and configuration
Windows 2003, AD and domain controller, Exchange 2007 SP2
With Public Folders
OWA can be accessed with a browser
https://myserver.com/public/Contacts can be access through browser
The credential used by the vb.net application is NetworkCredential
Using administrator credentials
When I run my code it throws exception 401 unathorized. Using EWS, it works. At this stage, I don't want to convert the code to EWS. Has anyone got a solution?
are you using the correct URL for SoapUI?
Point it to https://server/ews/exchange.asmx. Replace server with the dns name of your Exchange server.
Related
I'm having a hard time figuring out how to connect to an Azure Analysis Services using Azure AAD account with MFA.
I've installed the SSAS latest drivers.
I have Microsoft SQL Server Analysis Services (AdomdClient) as the data source type and I'm able to test the connection (it prompts for Okta MFA)
I'm able to create a dataset and use the query designer.
When previewing the report in VS, it returns this error:
The server did not provide a meaningful reply. This might be caused by a contract mismatch, a premature session shutdown or an internal server error.
If I change the data source to prompt for credentials, I receive this error:
Authentication failed: User ID and password are required when user interface is not available
Visual Studio 2019 16.10. Latest version of SSRS extension (2.6.11). Including power bi tag since it might be relevant too.
We faced a similar issue.
Ensure the user whose credentials you insert within the datasource are excluded from MFA within Azure AD policy.
Using filestream to upload documents into a SQL Server 2008 database. Database is on one server, and trying to upload a file from a different server via services.
Configurations
MSDTC enabled for both - Inbound, outbound...everything.
Connection is using Windows Authentication with Integrated Security=True in connection string.
Services which is trying to connect to DB is running on a domain account which has windows authentication on DB and is admin on DB.
Filestream is enabled in the database
Data folder of SQL Server has been provided full access to the domain user.
Data folder of SQL Server is not read only.
Windows firewall is disbaled - Private, Public everything.
But still we get the following error
Access is denied - OpenSqlFileStream
I guess, you may tried below link. Another option I may suggest is CLR Function.
http://www.codeproject.com/Articles/128657/How-Do-I-Use-SQL-File-Stream
Does anyone know how access a Access 2013 web app deployed on SharePoint via Azure? I have built an app and the db gets deployed into SQL Azure. I want to have full access to it via Azure. Is it possible?
After you publish the Access web application, then in the Access client you MUST enable external use. When you enable external use then a user name + password is generated for you. You can then view these values by again view the connections in Access.
These connection strings can be used in Excel, the sql management studio, or even a regular non web Access database. In fact such connection strings should work even for a web site and .net.
So just about anything can connect to these SQL Auzre tables, and the "enabling" of the connections is done from the Access client.
The connection opens are found via
File->and then click on mange connections. You see these options:
I have recently installed an exchange 2010 machine along side an Exchange 2007 machine. Everything is working except external EWS for mailboxes that I have moved to the 2010 machine mailbox database.
When I run Microsoft Exchange Web Services Connectivity Tests on https://www.testexchangeconnectivity.com for a mailbox that is on the Exchange2010 server, I get the message: The Client Access Server version does not match the accessed resource's Mailbox Server version.
I can however access the mailbox internally, by using the local exchange server 2010 address.
If I run the same test for a mailbox on the 2007 server it works.
I am not sure what to do to fix this. My autodiscover URL points to the Exchange 2010 machine.
I found out that this was being caused by the NAT. It was still set up to only go to the old exchange server. Once allowing port 443 and 25 to go to the new server it was all working.
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.