We have configured the visualsvn server in remote machine, while accessing the repository from the browser in our local machine, we are getting the below error in the internet explorer browser
'The XML page cannot be displayed'
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later
In the server machine's Event viewer, we found the log 'get /svnindex.xsl forbidden'.
Please note that we are able to connect the repository in TortoiseSVN & other subversion command line tools.
Is any setup or permission is needed to browse the repository in the browser ?
The account that runs VisualSVN Server service (the account is "Network Service" by default) must have Read & Execute permissions to %VISUALSVN_SERVER%. It seems that in your case the account does not have Read access to %VISUALSVN_SERVER%htdocs or %VISUALSVN_SERVER%htdocs\svnindex.xsl. Check the permissions in order to solve the issue.
Read the article KB37: Permissions required to run VisualSVN Server for more information.
Related
I am attempting to use Liquibase to deploy changes to SQL Server.
I have set up the sqljdbc jar file and placed it in my local maven repository. I then attempt to use the liquibase-maven-plugin to run the changes placed in the changelog for the given connection URL.
Here is what my connection URL is: jdbc:sqlserver://localhost:1433;user=Jenkins_BuildServices;password=hi;
I already created the login on my localhost and gave it sysadmin privileges. I also have made sure that the properties -> security is set to both SQL Server and Windows Authentication mode. Any ideas as to why the url being passed in is giving me back this error and not reading it from the URL?
trying to save file using Powerbuilder Datawindow Save As function
for path we are using
RegistryGet( "HKEY_CURRENT_USER\Software\Microsoft\windows\currentversion\explorer\shell folders", "Desktop", RegString!, ls_ret)
but when we login through citrix.
Not able to get this path.
When looged in as administrator getting this path but for other users we are not getting the path .
We also given full permission to particularly this registry but still not getting.
This does not seem to be Citrix specific, to simplify, add a user to Remote Desktop group and login directly via RDP (without Citrix), you should get the same behavior
I'm writing a script that periodically checks that certain services are running on remote workstations. I'm having a devil of a time getting an "SC \workst1 query" command working from one test machine to another. Both machines are running XP pro SP3. Neither is part of a domain. Both are in the same workgroup, and the administrator accounts have the same passwords.
I keep getting the "[SC] OpenSCManager FAILED 5: Access is denied" message, from either workstation to the other. I have tried using elevated privileges on both. Windows firewall software is turned off. There are no messages are showing up in the Event security logs. When (as administrator) I try going to "Computer Management" -> "connect to another computer" and access the remote services I get "Error 5 Access is denied".
I can set up a filesystem share between the two machines successfully, and "net use \workst1\IPC$ /user:Administrator" completes successfully, but the SC query still fails. I'm using IP addresses and not hostnames in these commands, but that doesn't help. I don't know what else to try. Thanks for the help.
Try to run the commans as a Administrator
start-> (type cmd in search box), right click on cmd, Run as a administrator -> execute your command
You must have administrative rights on the remote machine.
Moreover you must access the drive before calling "sc".
This can be achieved in command line using
net use \\remotemachine\admin$ <password> /user:<username>
admin$ is a hidden shared drive accessible to administrators that "sc" uses to control services.
I was having the same issue today trying to check if a service is enabled remotely.
I could solve the issue modifying the User Account Control for remote restrictions in windows:
To disable UAC remote restrictions, follow these steps:
Click Start, click Run, type regedit, and then press ENTER.
Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
If the LocalAccountTokenFilterPolicy registry entry does not exist,
follow these steps:
On the Edit menu, point to New, and then click DWORD Value. Type LocalAccountTokenFilterPolicy, and then press ENTER.
Right-click LocalAccountTokenFilterPolicy, and then click Modify. In the Value data box, type 1, and then click OK.
Exit Registry Editor.
More information about this solution in this site.
Your user should be remote, from Manage and Local users and groups
The UAC issue is obvious you have to pull down the lever for UAC setting
Also while installing the services you can use the following command
SC create SERVICENAME DisplayName= "DISPLAYNAME" binPath= "PATH OF EXE" start= disabled type= share
I have Openfire 3.7.1 installed on my Mac and have XAMPP installed aswell. I am having trouble configuring OpenFire. In the server settings I have given san-imac.local.lan as the domain name. The selected Standard database connection and picked MySql Database Driver. This is the databse URL jdbc:mysql://localhost:3306/test and given the username password of XAMPP phpmyadmin. But it says
A connection to the database could not be made. View the error message by opening the "/logs/error.log" log file, then go back to fix the problem.
First of all there is no such file in the /logs folder. What should I do to get this working and follow the procedures to get OpenFire up and running.
I need to build an app to connect to openfire for IM chatting like Gmail, Facebook, Yahoo using XMPP. If anybody could provide any guidance aswell, it will be very helpful.
Make Sure that your database is setup correctly including the name of your database, database username, and user's password. If you have this correctly configured then your opens ire should work just fine. Note that it will not accept if the database username has an empty password or not enough access rights to the database.
I hope that those hints will solve your problem.
check your password and username, I had the same error and it took me a while to figure out that I had my username wrong.
Resolved the issue.
log file is not getting created due to file write permission. To resolve this run OF server as follows
Run the openfire.sh file from terminal with sudo. This will start the OF with root access Now the error log file will be created.
My log file has error message as access denied to user #localhost. As I kept the user field blank in db connection page of openfire set up.
Keep the user field as root#localhost if u are using localhost.
I have reporting services running on SQL Server 2008 inside the domain. I'm able to hit http://localhost/reportserver without error. I can hit the same site from the web box (also in the domain name) using the internal ip of the DB box (192.169.X.X/ReportServer/ReportService.asmx.) I've looked in the SSRS logs and I see these hits being properly recorded, no errors.
However.. I have a website that uses the .NET ReportingService class to make a connection to SSRS. Using the same credentials as before, I get "Unable to connect to the remote server."
I've checked, there's no firewall active. Quadrupled checked the config in the web site to make sure it has the proper credentials and service URL for SSRS. There are also no hits in the SSRS logs when I'm trying to connect via .NET, so something is most certainly blocking access.
I've Googled my fingers bloody, and would seriously love some help. I'm sure it's some small thing, I just can't think of it.
The following change worked for me:
Remove the SSL configuration
1.1. Reporting Services Configuration Manager;
1.2. Web Service URL (click on Advanced button and then remove the SSL configuration);
1.3. Report Manager URL (click on Advanced button and then remove the SSL configuration);
Edit the file rsreportserver.config, normally it's in the path C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\
2.1. find out the Key SecureConnectionLevel;
2.2. change the Key's value from "2" to "0";
Could be your reporting services is exposed only to the private ip and your localhost. Try setting your domain name's static ip to the configuration. I've added a SSRS Url configuration link for your quick reference.
The following worked for me:
1. Remove the SSL if configured.
2. Go to C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config
3. In rsreportserver.config Change the SecureConnectionLevel value from "2" to "0"
The following worked for me: I Removed the SSL and set it to 0 vs 2 in the path
G:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer file is reportserver.config file.
Basically it was previously configured with SSL at port 443 but the server has been moved to another domain, and did not know where to go to get a new SSL certificate for this domain,
So i removed the SSL config in the reporting services configuration GUI and then remove it also in the reportserver.config file.
Make sure your report URL ends with /Reportserver/ (For the purpose of .NET code calling). Also keep in mind that you should use complete URL i.e. It should include servername and domain.
Check this link
I like the other solutions however in my instance I had to update the following. For some reason or another the service wasn't able to use 127.0.0.1, localhost, or any of the other IP addresses assigned to the computer, this method however worked.
Open "Report Server Configuration Manager"
Web Service URL
Click on Advanced Button
Click the IP entry that I wanted to edit.
Click "Host Header Name" and type in the fully qualified name for the server.
Report Manager URL
Click on Advanced Button
Click the IP entry that I wanted to edit.
Click "Host Header Name" and type in the fully qualified name for the server.
After the above were done both URLs in "Web Service URL" and "Report Manager URL" were able to work once correct credentials were passed to the server.