Configuration: IIS 7.0 / Windows Server 2008 SP2 / 32-bits
On the root node (the one named after the server name), when I look at Globalization, I see that some values are not default values.
I would like to find in which configuration file it is stored.
I already tried
...\Microsoft.NET\Framework\v4.0....\Config\Machine.config
...\Microsoft.NET\Framework\v4.0....\Config\Web.config
...\System32\inetsrv\config\applicationHost.config
None of them contains anything about
What have I missed?
First, there is nothing called Windows Server 2007. Maybe you are using Windows Server 2008.
Second, IIS Manager for 7.x reads ASP.NET settings from v2.0 folders, not v4.0. Only IIS Manager for 8.x and above read from v4.0.
Related
I've inherited an SQL Server 2008 R2 environment running on Windows Server 2003. I do not know if it was upgraded from SQL Server 2005 or if it was a freshly built out system. Due to issues with not being able to virutalize the physical server, it was decided to build a new, identical environment on a virtual server an migrate the databases and such to the new virtual server. We did decide to make one upgrade and that was to put Windows Server 2012 on the new server. We kept the instance name and server name the same (these were modified after we took the old physical server offline). I kept the file paths and folder names the same as well on the new server. I migrated the SSIS packages from the old server to the new server using the Export option in Integration Services (right click on the package>Export Package). The packages were stored in MSDB on the old server. I copied the config files from the old server to the new server and kept them in the same file location as they were stored on the old server. Ok, so here's my problem. When I started all of the SQL Agent jobs, several of the ones that used SSIS packages failed. After researching the issue, I
discovered it was due to the SQL provider string (Provider=SQLNCLI) was set to Provider=SQLNCLI.1, which is for SQL Server 2005. Once I changed this to Provider=SQLNCLI10, all was good. A caveat to this is that other packages that are using Provider=SQLNCLI.1 and are working just fine. The question that is eating at me is this, why were these packages running successfully on the old server which was running the same version of SQL Server when SQLNCLI.1 is supposed to be a setting used in SQL 2005 AND why are some packages working successfully still using SQLNCLI.1 and other had to be changed??
the execute of some packages depends by the structure of this file.
the are some task or some expression or some parameters that have been redefined in the new releases.
I feel that the title pretty much speaks for itself. I keep getting a server 500 error when i try to access a page on my site that is using the Access DB.
I created an ODBC (32 bit) Data Source using the driver Driver do Microsoft Access (*.mdb).
I am sure i am using the wrong drivers/IIS configurations. This used to be hosted on an old server and we are trying to move everything over.
Would anyone be able to point me in the right direction? Thanks!
EDIT
I was able to get errors printed to my page. Below is the following error:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found
and no default driver specified
When I enable 32-bit Applications I get the following error:
HTTP Error 404.17 - Not Found
The requested content appears to be script and will
not be served by the static file handler.
This issue is related to running 32bit applications on a 64bit server. Furthermore, if you have installed something else on it (for example, Outlook Web Access, or OWA for short) it can disrupt the IIS with adding it's 64bit modules to load globally, and that would effectively cause errors on 32bit pools.
The following debugging is assuming you have a requirement to run 32bit ASP application on a 64bit IIS server.
You have to set your application pool to run as 32bit
If the 32bit pool stops right after you make a request for an ASP page, it means that most probably there are 64bit modules failing to load. You need to see which dll is creating the issues by viewing the Windows Event log (eventvwr). Then, one by one, you edit the applicationHost.config file and add preCondition="bitness64" to each module that you see in the eventvwr until you get rid of all the errors in the log.
When finished with step #2, your pool should be working, but your app might not - it will most probably report 404.17, even if there is an ISAPI handler for ASP. When you open IIS, on the left side choose the server and on the right open the ISAPI and CGI restrictions. You will see that there's an ASP entry there (if not - you need to install it as a feature on the server). The ASP might point to something like %windir%\system32\asp.dll, but you need to make another entry. Your appPool is running as 32bit on a 64bit machine (that's shortened as WOW64 = 32bit Windows application running on Windows 64bit - Windows on Windows64), and you need to add an asp from %windir%\SYSWOW64\asp.dll. Also, add the corresponding handler (navigate to handlers, and practically repeat the entry for asp but use the SYSWOW64 folder instead of system32)
This should (finally) get it working.
I'm using SMS 2008 & I'm looking for where the registered servers are stored on my local machine. I have searched the registry with no luck.
They are kept as an XML document here:
%APPDATA%\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSrvr.xml
On Windows XP this resolves to:
C:\Documents and Settings\username\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSrvr.xml
Note: As of Windows Vista there is no Application Data folder, and the path resolves differently.
For Windows 10 and SSMS version V17 the document can be found using this path in windows explorer
%APPDATA%\Microsoft\SQL Server Management Studio
Or this powershell command
dir "$env:APPDATA\Microsoft\SQL Server Management Studio\RegSrvr.xml"
Example
Directory: C:\Users\george\AppData\Roaming\Microsoft\SQL Server Management Studio
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 19/02/2019 4:04 PM 60998 RegSrvr.xml
In windows 8 and 7 here is the correct path.
C:\Users\username\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\Shell\RegSrvr.xml
I'm trying to install the SSRS data connector for my CRM4 implementation.
I'm using the Method 2: Modify the Install-config.xml file from this page. But keep getting the same error message:
Unable to validate SQL Server Reporting Services Report Server
installation. Please check that it is correctly installed on the local
machine.
I've added the following to my XML file.
<reportserverurl>http://SSRS-Server/Reportserver$MYORG_MSCRM</reportserverurl>
<instancename>MYORG_MSCRM</instancename>
Anyone know what is still wrong?
I tried several instance names but they all don't work either.
I can access my SSRS server by going to http://SSRS-Server/Reports and it will give a list of all services running there.
Any help would be much appreciated.
You may need to post more details regarding this issue:
1) The 2nd method described in this link : here is used when the Reporting Server database is installed using the SQL Server named instance. Are you installing the Reporting Server database in the default instance or named instance ?
2) If you are using default instance, you might not need to use custom XML, you can just run the installer without requiring the input XML file.
3) What is the architecture of your CRM implementation ? is the CRM Application, SQL server and Reporting Server resided in the same server ? or different server ?
Hope this helps.
I realise this is a really old article however I wanted to post the resolution I found to work as I have spent the past 3 days trying to resolve this issue! I created an account just to post this.
I was having the same problem as the original article. I had SSRS 2008 installed on a server, CRM (4.0!!!) on a different server and SQL 2008 on a different server again. When all permission issues were resolved and ports were opened from the SSRS server to the SQL server, I was still having problems getting the SetupSrsDataConnector.exe to see the locally installed instance of SSRS2008 (Not R2).
I found the resolution to the issue in this article:
https://community.dynamics.com/crm/b/pabloperalta/archive/2011/07/12/unable-to-validate-sql-server-reporting-services-report-server-installation-error-while-installing-srs-data-connector
Effectively the problem I was having is that my copy of the SRS Connector installation files were old and needed updating, however my server did not have internet connectivity. In the link above, it gives you a download location to get a .mps file which contains the updates for the SRS Connector.
You need to download this .mps file and then run the installation via command prompt with a customised install-config.xml file, which specifies the SSRS ReportServer URL and the SSRS Instance Name in a custom tag (what you named the SSRS instance when you installed it) and another custom tag for <Patch update="true">C:\Path to the .msp file< /Patch>
This was my installation command:
"D:\Stage\SRSDataConnector\SetupSrsDataConnector.exe" /CONFIG "D:\Stage\SRSDataConnectorUpdates\install-config.xml"
Does any one know how to connect to MySQL 5.1 with Visual Studio 2010?
I have already tried the MySQL Connector/ODBC route and it got me really nasty results. The table rows were all listed as a view in the views section and nothing at all was listed in the tables or procedures folder.
To get the Entity Frame working with VS2010, I had to do the following:
This only worked with Mysql .net Connector v6.3.1 (alpha). Previous versions ignored VS 2010 (click Development Releases)
I had to rename my Framework\v1.1.4322\CONFIG folder. Otherwise the install will fail. Rename it back when finished
(I've blogged about this here)
Update
6.3.2 is in beta and I can confirm this works. (I didn't need to rename the framework folder)
this seems to solve the issue
UPDATED LINK TO LATEST RELEASE THANKS #Christian Payne
Update: looks like there is already a non-beta!!!!
http://www.mysql.com/downloads/connector/net/
As someone else suggests..
http://dev.mysql.com/downloads/mirror.php?id=382641
..fixes the problem.
I had v6.2.3 installed after I had vs2010 installed and the MySQL driver was not shown in the list of the Database Connect dialog. I wrongly assumed I should use the .NET ODBC drivers instead and it caused all sorts of problems. Although I could easily connect to the DB using codebehind, the server explorer wouldn't connect to the DB.
Luckily after uninstalling 6.2.3 and installing 6.3.0 (from the link above) the MySQL driver was added to VS2010, and I was able to connect to the database and see it in my server explorer.
http://bugs.mysql.com/bug.php?id=45122
I was able to get this to work by doing the following:
My Environment:
Development Box -- Win7 64bit,
VS2010 Pro
Deployment Box -- Win2k8 svr with IIS7
running ASP.NET .Net 2.0/3.0/3.5 sp which is
hosted at DiscountAsp.Net (Note:
DiscountAsp.Net does not provide a
MySQL DB when running on a Win2k8
svr, I'm using a MySQL DB that I connect
to elsewhere on the InterWebs)
Steps I took:
Installed MySql.Data, Version=6.3.6.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d
Ref'd the .Net 2.0 version of the MySQL assembly in my ASP.NET MVC2 Web project set to target .Net 3.5 (the path for the MySQL assemblies I used was C:\Program Files (x86)\MySQL\MySQL Connector Net 6.3.6\Assemblies\v2.0)
I ref'd all 3 of the MySQL assemblies (MySql.Data.dll, MySql.Data.Entity.dll & MySql.Web.dll)
I marked each of those assemblies as "Copy Local=True" in my project (a.k.a bin deployment)
Added a MySQL DB connection string to my Project (using the MySQL provider)
Added an ADO.NET Entity Data Model to my project in VS2010 using the connections string
VS2010 took about 30 secs to chew thru my MySQL DB schema but then provided me with a beautiful GUI interface to tweak my MVC Models
Used the DB Entities in my MVC controllers
Deployed the app to my hosted server at DiscountAsp.Net
It works like a charm :)
Erm... through code? Or do you mean the server explorer add-in? Have you tried the latest (albeit GPL-ed) connector version for .NET from Mysql themselves? Again, it's GPL-ed so be aware of the consequences of using that for your own software.
Microsoft Visual Studio 2010 Beta 2 is busted for DDEX providers. They are auto promoting a VS 2008 assembly from 9.0 to 10.0 and it fails. The failure has to do with the fact that a .NET 2 assembly cannot load a .NET 4 assembly.
This worked in beta 1, so it is something they broke.
I even went back and tried the reference DDEX provider from the SDK. It won't load in VS 2010 beta 2 either. That tells me they have something that needs to be fixed.
When is the next beta?