SQL Server 2008中的Reporting Services安装[发布] 1(Reporting Services Installation in SQL Server 2008 [Release] 1)
我们已经安装了SQL 2008 Server(第一版)的完整版本并从下载(几年前)获得许可。 现在我们进入Reporting Services; 但是,似乎只安装了Reporting Services的Express版本。
在服务下的控制面板中,我只看到列出的“SQL Reporting Services(SQLEXPRESS)”。 [Express也在服务器上]
我认为最初安装时不会选择Reporting Services选项。 我想回去更改安装,但是我找不到SQL 2008 R1安装盘或下载。
任何建议? 谢谢。
We have the full version of SQL 2008 Server (first release) installed and licensed from download (a couple years ago). Now we are getting into Reporting Services; however, it seems only the Express version of Reporting Services is installed.
In the control panel under Services, I only see "SQL Reporting Services (SQLEXPRESS)" listed. [Express is ALSO on the server]
I do not think the Reporting Services option was selected when we initially installed. I would like to go back and Change the installation, however I cannot find the SQL 2008 R1 installation disk or download.
Any advice? Thanks.
原文:https://stackoverflow.com/questions/5858804
最满意答案
将权限755设置为必要的文件和文件夹
你在这个问题上遇到了困难。 对于需要除755之外的其他权限的项目,权限已更改。
需要注意的基本事项是必须可写的文件和目录:
- file: magento/var/.htaccess - directory: magento/app/etc - directory: magento/var - all the directories under: magento/media chmod o+w var var/.htaccess app/etc chmod -R o+w media
Set permission 755 to necessary files and folders
You've hit a rock on this one. The permissions have been changed on items that need other permissions than 755 set.
The base things to watch out for are the files & directories that must be writeable:
- file: magento/var/.htaccess - directory: magento/app/etc - directory: magento/var - all the directories under: magento/media chmod o+w var var/.htaccess app/etc chmod -R o+w media
相关问答
更多-
Apache日志:请求超出了10个内部重定向的限制(Apache log: Request exceeded the limit of 10 internal redirects)[2023-05-08]
这些规则创造了无限循环 RewriteRule ^(.*)\.css$ $1.css [L] RewriteRule ^(.*)\.png$ $1.png [L] RewriteRule ^(.*)\.jpg$ $1.jpg [L] RewriteRule ^(.*)\.gif$ $1.gif [L] RewriteRule ^(.*)\.js$ $1.js [L] RewriteRule ^(.*)\.swf$ $1.swf [L] 顺便说一下,没用(所以你可以删除它们)。 您的代码中也存在许多设计问题 ... -
很难注意到打字错误。 其中一个conds中的最终参数之间没有空格。 这里更容易发现: RewriteCond %{REQUEST_URI} !foo/[NC] < - 失败 RewriteCond %{REQUEST_URI} !foo/ [NC] <-works It was just a hard to notice typing mistake. There is no space between the final parameters in one of the conds. It is easi ...
-
我怀疑问题规则是你指出的规则。 在重写一次之后,假设index.php确实存在,由于第二个条件( !-f ),它不应该再次匹配。 然而,第二条规则会将index.php添加到网址直到永恒。 为防止将来出现问题,您还应将重定向规则移至所有其他规则之上。 我建议只使用临时重定向,直到.htaccess中的所有内容都经过测试并按预期工作。 永久重定向被缓存,如果你在某个地方犯了错误,那么在你经历清除缓存的痛苦过程之前,你所做的任何更改都是不可见的。 RewriteEngine On RewriteBase / ...
-
由于这些规则,你有一个重定向循环 RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) /app/$2 [L] RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ /app/$2 [L] 实际上,你必须记住,即使在重写之后,你的规则也会被评估。 因此,如果您有/something/wp-xxx/yyy/zzz ,它将在内部重写为/app/wp-xxx/yyy/zzz 。 但是现在,如您所见,您的规则将与新的uri /app/wp-xxx/yyy/zz ...
-
你可能有一个递归的redirect_to方法。 看着日志, redirected from r->uri = /index.php 此redirected_to显示超过10次,因此请检查您的相关控制器,或发布它。 The problem came from an .htaccess in /var/ which affected my site in /var/landing-page.
-
您的条件应该意味着rewrite if not already /subdir但它正在反向。 尝试这个: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_URI} !^/(subdir|favicon\.ico) RewriteRule ^ subdir/index.php [L] Your conditions should mean rewrite if not ...
-
尝试只使用这一个来重定向/host/...到/host/index.php... RewriteRule ^/?(?!index\.php)(.*)$ index.php?lang=$1 [NC,L] (?!index.php)是否为前瞻性,以检查开头是否没有index.php 。 所以它不会像/index.php?lang=...那样触及网址以避免递归。 Try with only this one to redirect /host/... to /host/index.p ...
-
将权限755设置为必要的文件和文件夹 你在这个问题上遇到了困难。 对于需要除755之外的其他权限的项目,权限已更改。 重置文件权限 需要注意的基本事项是必须可写的文件和目录: - file: magento/var/.htaccess - directory: magento/app/etc - directory: magento/var - all the directories under: magento/media chmod o+w var var/.htaccess app/etc chm ...
-
哪个vhost导致错误请求超出了error.log中的重定向(Which vhost causing error request exceeded redirects in error.log)[2023-05-04]
也许,我首先会在错误日志中记录违规重定向的确切时间戳查看访问日志。 从访问日志中,您至少可以看到引用者找出导致它的虚拟主机。 Probably, I would start by looking through the access logs at the exact timestamp that the offending redirects are logging in the error log. From the access log, you can probably at least see r ... -
RewriteEngine On RewriteBase / RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ index.php?/$1 [L] 这对我有用。RewriteEngine On R ...