I've got SQL Server 2008 with SSIS/SSRS installed on my development box. I followed through the installation notes and everything appeared to install just fine - no errors or anything. I've got it configured using all the defaults for now until I figure out what is what. So the server can be accessed via http://localhost:80/ReportServer and the reports via http://locahost:80/Reports.
I've created a dummy report against the AdventureWorks database to test report creation and deployment and after some initial headaches which were resolved by running BIDS as an administrator, I'm having problems accessing the reports via the web interface and indeed, I'm having the same issue accessing the report server via the web interface.
When I open the URLs in any browser - IE/Firefox/Chrome they all prompt me for credentials. My dev box isn't part of a domain and the credentials I use to log into the machine don't appear to be what it is after as they don't connect successfully. I don't really understand why it's asking for credentials at all due to the fact that the address is an intranet address. In either case, IE is configured to pass through my Windows credentials when logging into machines on the intranet.
Did I configure something incorrectly when I set it up? Does anyone have any decent tutorials for not only installing SSRS, but configuration for development machines.
Try opening your browser with elevated (Administrator) privelages. Did that help?
This may also be related...
http://blogs.msdn.com/b/lukaszp/archive/2008/07/18/reporting-services-http-401-unauthorized-host-headers-require-your-attention.aspx
Related
Linked from here
I've been tasked with setting up some VMs. I've been given some admin details but no further guidance. The server is a fresh install.
My problem is that I'm on Linux/OSX and don't want to run Windows aside from setting up after which I hope to be able to manage things through the web client.
I think there is an ESXi installation. This would be Version 6. How do I set up the web client?
I've installed vSphere Client on a local Windows VM.. not sure what to do with it though.
The documentation is pretty awful and there hasn't been much useful info on the net. I'm really stuck as I didn't set these up and haven't used servers like this before, so I have no context or understanding of the VMWare ecosystem beyond using a virtual machine locally! (even then I've preferred Virtualbox)
Any advice would be amazing
p.s accessing https://[ipaddress]/vsphere-client does not work. Produces a blank browser page... with no html served as an error
If you have the name of the server on which the VMs are stored, type this into the URL of a web browser then it gives you management options or alternatively use this login screen:
I'm currently implementing the Class 2 WebDAV server on my company's MVC / noSQL web app. I'm developing it locally on my machine using visual studio 2013, IIS 8.5, Windows 8.1 and word 365. The documents are stored in the noSQL database.
I've managed to get it working in the past, however recently word refuses to connect to the WebDAV server. When I click the document link it open word and the following error appears:
{ correct web address} cannot connect to server.
I have used your built in logging tool and fiddler to see if any requests are made to the server and there are none.
Are there any steps or suggestion you can make to help me debug this problem.
After reading the documentation a few times and trial and error I found that word was caching in the registry. I followed the instructions and rebuilt my project and it seems to have worked.
http://www.webdavsystem.com/server/documentation/ms_office_read_only
Clear Microsoft Office WebDAV cache in registry. Microsoft Office reads WebDAV server options when connecting to server first time and stores them for later use. If your server settings has changed during development (or you just fixed some server issues) you may need to delete this settings. The Microsoft Office WebDAV cache is stored under the key:
HKEY_CURRENT_USER\Software\Microsoft\Office\\Common\Internet\Server Cache\
To clear cache just delete all keys under this key. In a development environment we suggest always clearing the cache if your WebDAV server class has changed or after authentication scheme has changed. As an alternative to deleting cache, you can just reconfigure your server to run on a different port.
Note that in production environment usually you do not need to clear this cache or change port as soon as you server settings do not change often while Microsoft Office will re-request server options after some time.
As soon as your code worked in the past and now stopped working I guess that the trial period, which is 1 month, of IT Hit WebDAV Ajax Library has ended. Are there any errors in the web browser console? To start a new trial period just redownload it here.
I know this question has been asked several times but I have a slight variance on it that I have been trying to resolve.
I have crystal reports running on an old web system written in classic asp. All the reports have been running without problems for several years, however recently security was improved so that the system is now accessed over HTTPS. Since this change the reports have all started asking for the database credentials. If SSL is disabled so that it returns to regular HTTP then they start working again.
The system was created by another developer who has since moved on so I am not very familiar with it, but as far as I am aware the reports are all set to use a System DSN set up in the control panel of the server that IIS is running on. The database is located on a separate server.
Does anybody have a suggestion as to why the reports would start asking for database credentials after changing to HTTPS and how to resolve it? I will not be able to make any code changes to the application as the source code is not available but I can modify the reports and play with connection settings etc.
I have figured out the problem. The site was running HTTPS but the button for the report was in a form which submitted to HTTP and then was redirected back to HTTPS. This was causing a loss of the session information or something like that. Fortunately the forms action url was stored in the database so it was a simple matter to resolve.
So I've been running CF9 on Linux for a while and using CFMail to send email through a client's Exchange 2010 server for quite a while.
We're attempting to migrate to CF10 on Win2008, IIS7.5. Everything is set and ready to go except I can't get CF10 to verify the mail connection? I've got both mail settings (CF9 and CF10) set the exact same way and can view them open side by side and verify they're identical. However, while the CF9 verifies successfully the CF10 system fails??
I tried sending through CFMail tags while specifying the server credentials and see this in the CF10 log:
"javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client"
What does this mean? I know my authentication credentials are correct because I'm able to connect in CF9.
I've turned off all firewalls and still nothing. So, I then tried installing CF10 on my Mac laptop. It, too, will not verify the mail connection!
Is there a known problem with CF10 connecting to an Exchange mail server?
Any ideas?
I "solved" this.
I could find little online and received no comments to this thread. No combination of settings I tried would work and I have no access to the client's mail server. The person who runs that server couldn't run a lemonade stand so no help there.
Then I stumbled across this page. Nothing to do with ColdFusion but seemed like a similar issue.
Recent changes in the JavaMail API has changed certain authentication
defaults and sometimes will create an authentication error with some
Exchange Server environments dependent on the configuration.
I'd never put much thought into CFMail because it was always drop dead simple and simply worked. Focusing on this link's Resolution 2 (ie replace the mail.jar with an older version). I wondered if CF used JavaMail and if I could downgrade CFMail? I cracked open CF's mail.jar file and found that CFMail does, indeed, use the JavaMail API. So, I then checked the ColdFusion docs to see if any new features were added to CFMail between CF9 and CF10. None.
So, I swapped out the mail.jar file from my CF9 install to CF10 and restarted. Boom! Everything worked immediately. As far as I can tell I've had no compatibility issues to report.
Swapping the mail.jar did not work for me. However, adding the following to JVM arguments
-Djava.net.preferIPv4Stack=true
worked for me. Please refer to the following article
Java Mail mystery - SMTP blocked?
posted by another user
Does full trust mean the same as Run As Administrator? I have read things stating that "for this to work, the application must be a full-trust application." Is that the same as you must have administrator privileges to run the application? If not, what's the difference? How can you tell if an app is "full-trust"?
I am told that "Administrator or not, .Net apps won't do certain things if they aren't running from a 'trusted' location." What is a "trusted location"? If you run an app from a "trusted location", can you do things that "require full-trust" without being an administrator?
No. Full-trust is a .NET term used to indicate that it's not running in a reduced-priviledge .NET sandbox. In .NET prior to 3.5 SP1, this included running from a network share (in the default configuration). It also includes running as a ClickOnce application that has not requested additional permissions, or in some other browser-based sandbox.
Full-trust means it can do anything the user it is running as can do, not that is running as an administrator.
No. As of version 2.0, the .Net framework has it's own little filesystem setup for security. Administrator or not, .Net apps won't do certain things if they aren't running from a 'trusted' location.
Just about anything on your local hard drive is trusted, but (and supposedly they fixed this for 3.5sp1) even the local intranet is not trusted, so most .Net desktop apps will fail to even start if they're sitting on a network drive or share.
You can change the configuration on a machine so it will allow apps from that zone, but it has to be done for every machine that's going to run the application, which breaks a common corporate deployment scenario.
From an ASP.Net standpoint, it also means that certain activities require more 'trust' than others. Sending e-mail, for example, can cause exceptions if not set up correctly.
Basically Full Trust means that the C# code has total control over the current (.Net) process and all processes running under the Application Pool account.
It is the same as running a C++ dll
Admin access will depend on the IIS settings (ie. if you run the website under System or an admin account)