Database timeout

Hello,
I am relatively new to SAP Business One. The company is just starting to get our feet wet with SAP. We have some quirks that need to be resolved. One such quirk seems simple to fix but its driving me nuts. I have a user who is trying to do Production Receipts - after she enters the information and clicks 'update'...SAP hangs. Eventually a database timeout error will appear at the bottom.
I have tried multiple computers, re-installed the client, installed the client on a PC that did not previously have SAP B1 client installed, and played around with networking settings. When she enters production receipts on other PC's - it works just fine...no errors appear. It seems like a very random issue. I am not sure if this is an SAP issue or related to the PC.

8.00.178 SP:00 PL: 44
I did uninstall and reinstall the client on the users PC. I also installed the client on a laptop which did not have a client previously installed.
I am going to rebuild a computer, install everything from scratch and try that.

Similar Messages

Excessive database timeouts. How to monitor?

Hi
There are excessive Timeouts being recorded on the database. using db console or OEM what is the best way to investigate this, and the reasons behind it?
Thanks.
Oracle 10.2.0.2.0.
DA

not sure how you would monitor this in oem or dbcontrol. it may not be oracle timing out the session. from a troubleshooting aspect I would look at client sqlnet trace or maybe setup dead connection detection by setting / tuning sqlnet_expire_time in your sqlnet.ora which should help reduce timeouts.

Database timeout issue in oracle 11g 64 bit windows machine

Hi ,
Database connection getting timedout for every 30 seconds in oracle 11g database 64 bit windows environment.
And the error we are getting is "Invalid user name and passoword".
After altering the schema passoword
alter username identified by pwd;
we are able to connect to database but it is getting timedout after 30 seconds.
Is there any parameter settings that requires changes or verifications.
We are facing this using sqlplus as well as through JDBC connection.
Thanks
Prasanna

Check profile assigned to user... there is a parameter idle_time.. increase this..

Connecting to mySQL database, timeout error

I am having problems connecting to my database, here is the connection class
public class DBConnect
    public static Connection getDBConnect() throws Exception
        String x = "worked";
        //String url = "jdbc:mysql://mysql8.secureserver.net";
        String url = "jdbc:mysql://mysql13.secureserver.net/DBName?user=User&password=Password";
        System.out.println("Before driver load");
        try
            Class.forName("com.mysql.jdbc.Driver");
            System.out.println("Driver Loaded");
        catch(java.lang.ClassNotFoundException e)
            System.err.print("ClassNotFoundException: ");
            System.err.println(e.getMessage());
        System.out.println("After driver loaded and Before connect");
            Connection con = DriverManager.getConnection(url);
            System.out.println("Tried connect");
            return con;
}here is the error:
INFO: Server startup in 17685 ms
com.mysql.jdbc.CommunicationsException: Communications link failure due to underlying exception:
** BEGIN NESTED EXCEPTION **
java.net.SocketException
MESSAGE: java.net.ConnectException: Connection timed out: connect
STACKTRACE:
java.net.SocketException: java.net.ConnectException: Connection timed out: connect
     at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:151)
     at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:280)
     at com.mysql.jdbc.Connection.createNewIO(Connection.java:1765).....

4. The username and password are incorrect, and it's
hanging waiting for you to enter new ones. (I've had
this happen before with Oracle).Sir,
A good point but MySQL will just bomb out in this case.
Another possibility is do you have the latest JConnect driver? The old drivers have protocol issues talking with the newest versioned servers.. but the new drivers are backwards compatible.
Sincerely,
Slappy

After adding seperate performance collections to MAP 9.1 database, the database has become corrupted

Hi,
I have installed MAP 9.1(9.1.265.0) on my notebook, with Windows 7 Enterprise. The inventory of our environment was successfull and I have successfully added some performance collections to the database.
First I ran the performance collection for one hour, then added a performance collection of one week. this was okay.
Then I waited one week and added another collection of about five days. That collection would not stop: It was scheduled to run between 2014-07-28 12:49:31 until 2014-08-01 05:00:04. But it was still running at 2014-08-01 05:30:25. I waited for a little
bit longer, but the collection kept on running according to the status screen.
So I cancelled out of the collection at 2014-08-01 05:45. In the performance data it said that the colection ran from Jul 14 2014 08:04 AM until Aug 1 2014 4:57AM. So that looked okay.
But now, when I try to Get the performance metrics data from MAP, it states that I have to do a "Refressh Assessment", because I problably have cancelled out of a collection. This "Refresh Assessment" wil run for about an hour and than
completes with a message "Failed"
I get these errors in the MapToolkit.log
<2014-08-05 05:14:51.09
AssessInventoryWorker@StoredProcAssessment,I> RunAssessment() - [Perf] [[Perf_Assessment].[ClearPerfdata]] : 125 ms
<2014-08-05 05:14:56.13
AssessInventoryWorker@StoredProcAssessment,I> RunAssessment() - [Perf] [[Perf_Assessment].[CreateTimeIntervals]] : 5039 ms
<2014-08-05 05:22:47.76
AssessInventoryWorker@StoredProcAssessment,I> RunAssessment() - [Perf] [[Perf_Assessment].[CreateMetricsPerTimeInterval]] : 471591 ms
<2014-08-05 05:52:54.66
AssessInventoryWorker@DataAccessCore,W> DoWorkInTransaction<T>() - Caught InvalidOperationException trying to roll back the transaction: This SqlTransaction has completed; it is no longer usable.
<2014-08-05 05:52:54.79
AssessInventoryWorker@DataAccessCore,W> DoWorkInTransaction<T>() - Caught a SQL transaction timeout exception. Will retry 3 more time(s). Retrying in 5000 milliseconds.
<2014-08-05 05:53:15.86
AssessInventoryWorker@DataAccessCore,W> OpenConnection() - Caught a SqlException trying to connect to the database. Will retry connection 3 more time(s). Retrying in 5000 milliseconds.
<2014-08-05 05:53:20.99
AssessInventoryWorker@DataAccessCore,W> OpenConnection() - Caught a SqlException trying to connect to the database. Will retry connection 2 more time(s). Retrying in 10000 milliseconds.
<2014-08-05 05:53:45.00
AssessInventoryWorker@DataAccessCore,W> OpenConnection() - Caught a SqlException trying to connect to the database. Will retry connection 1 more time(s). Retrying in 15000 milliseconds.
<2014-08-05 06:24:03.69
AssessInventoryWorker@DataAccessCore,W> DoWorkInTransaction<T>() - Caught a SQL transaction timeout exception. Will retry 2 more time(s). Retrying in 10000 milliseconds.
<2014-08-05 06:54:13.91
AssessInventoryWorker@DataAccessCore,W> DoWorkInTransaction<T>() - Caught a SQL transaction timeout exception. Will retry 1 more time(s). Retrying in 15000 milliseconds.
<2014-08-05 07:24:28.99 AssessInventoryWorker@Analyzer,E> RunAssessments() - Assessment threw an exception:
<2014-08-05 07:24:29.03
AssessInventoryWorker@AssessInventoryWorker,I> AssessmentCompletedEventHandler: Assessment completed event.
<2014-08-05 07:24:29.09
AssessInventoryWorker@TaskProcessor,I> WorkerCompleted: Worker: 'AssessInventoryWorker'
<2014-08-05 07:24:29.15 TID-16@TaskProcessor,I> Run: Completed. Status: Failed
Is there maybe a restriction to the intervalls of adding performance collection data, or is there something else I am doing wrong?
(I made a backup of the database after the first week of performance data, that database is still usable, so I can try to add more performance collections to that version of the database)
I hope someone has an idea what is going on.
Thanks!

Time between isn't the problem. If you look in the log file, SQL is timing out. I think the problem is machine resources and time related. After the performance data collection has run for the predefined amount of time, MAP has SQL execute various assessments
on the data to aggregate the raw data into something MAP can use. The more raw data that exists, the longer SQL will take and the more CPU and memory resources SQL will need.
I would recommend that you have at least 4 cores or vCPU's and 6-8 GB of memory dedicated to the machine on which MAP is running. I would also follow the directions in this Wiki article to increase the timeout in MAP so that MAP will give SQL the time it
needs to complete the job.
http://social.technet.microsoft.com/wiki/contents/articles/10397.map-toolkit-increasing-the-sql-database-timeout-value.aspx
Please remember to click "Mark as Answer" on the post that helps you, and to click
"Unmark as Answer" if a marked post does not actually answer your question. Please
VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

Error while trying to setup a standby database.

While tring to setup a standby database (with version 8.1.7.0.0) i am running the command:
recover managed standby database timeout 20;
Here is the errors i'm getting:
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/data/syndicate/standby/system/dup75_system01.dbf'
ORA-16016: archived log for thread 1 sequence# 6518 unavailable
Although it says that file 1 was not restored from sufficiently old backup I've copied all the datafiles from the primary database at once - using a script.
The archived log sequence it asks for is non-existant - the last one i have is # 6517.
Thank you guys in advance for any ideas.
Greg

I am having the same problem as you are when I am applying the current logs after successfully mounting standby database as seen below:
SVRMGR> alter database mount standby database;
Statement processed.
SVRMGR> recover standby database ;
ORA-00279: change 2939586 generated at 07/28/2002 01:09:33 needed for thread 5718
ORA-00289: suggestion : C:\ORACLE\ORADATA\STANDBY\ARCHIVE\STANDBYT571S00362.ARC
ORA-00280: change 2939586 for thread 5718 is in sequence #362
Specify log: {=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'C:\ORACLE\ORADATA\STANDBY\SYSTEM01.DBF'
SVRMGR>
Just before copying the datafiles from the primary database I did the following:
Connected to the primary database:
1. alter database create standby controlfile as .....
2. alter system switch logfile
3. shutdown normal
4. took a cold backup (including archived redo logs)
Copied the data files, redolog files, archived redo logs and standby controlfile to standby database:
1. made copies of standby controlfile over current standby ones.
2. startup nomount (the standby database)
3. alter database mount standby database;
4. recover standby database;
That's when it asks for an archived redo log that does'nt exist and when I enter cancel, that's when I get the above error?
Am I not applying the latest redo logs to the latest cold backup of the primary database?
Your help would be much appreciated!

VS2013 suddenly unable to read database schema on Azure server

Hi,
I have 2 databases on an azure server. Everything worked well until yesteday: VS2013 is now unable to read any database schema on this Azure server (same operations on an SQL EXPRESS instance are performed without problem).
When I try to open any table definition, I have "the designer encountered an error while loading the table definition"
When I try to rebuild after update the model (EF6) from database (I added a stored procedure), I have:
"The target database schema could not be retrieved. Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. " (note that when I launched "update
model from database", I had no problem. The fuss happens during the build).
But I still can read data and execute procedure from Azure using VS 2013. I did not alter any credential. Using the same credentials, I still can create/update tables/procédures from Azure portal.
I am a very basic user of VS2013 and Azure, I did not install or create anything weird on it.
I emphisize same operations on an SQL EXPRESS instance are performed without problem.
Thanks for help.
Olivier

Hello Olivier,
Sorry for the inconvenience because of the above issue.
Could you please try the new SSDT (preview) tool and check if you are able to get the table definition or not.
http://blogs.msdn.com/b/ssdt/archive/2014/12/18/sql-server-database-tooling-preview-release-for-the-latest-azure-sql-database-update-v12-preview.aspx
Download link : http://www.microsoft.com/en-us/download/details.aspx?id=45319
Thanks,
Mukesh

Error deploying data tier application to SQL Azure at "Registering metadata for database" step ... should I care?

I'd like to move an on-premesis SQL Server Database to SQL Azure. I've used SQL Mgmt Studio to Extract Data Tier Application and save my db as a dacpac file. Now I'm connected to my Azure server and I've chosen to Deploy Data Tier Application. I select my
dacpac and the deploy starts but then on the last step "Registering metadata for database" it times out. I've tried it a couple of times and each time the deployed database is there and appears to be fully populated, but I'm not sure if I can ignore
that error and continue. What is supposed to happen in that step, and should I expect it to fail when deploying to SQL Azure?
I'm following the steps here http://msdn.microsoft.com/en-us/library/hh694043.aspx in the Using Migration Tools > Data-tier Application DAC Package section, except that to deploy there's no SQL Mgmt Studio > Object Explorer [server]
> Management >"Data Tier Applications" node, so I'm deploying by right-clicking on the server name and choosing "Deploy Data-tier Application".
My (total) guess here is that it's deployed the database fine and it's doing whatever magic happens when you register a data tier application, except that it's not working for SQL Azure.
I'm running against a server created for the new Azure service tiers, not against a Web/Business edition server.
The full details of error I get are below.
thanks,
Rory
TITLE: Microsoft SQL Server Management Studio
Could not deploy package.
Warning SQL0: A project which specifies SQL Server 2008 as the target platform may experience compatibility issues with SQL Azure.
(Microsoft.SqlServer.Dac)
ADDITIONAL INFORMATION:
Unable to register data-tier application: Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft.Data.Tools.Schema.Sql)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Microsoft SQL Server, Error: -2)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.9213&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
The wait operation timed out
BUTTONS:
OK

Hello,
The registration process creates a DAC definition that defines the objects in the database, and register the DAC definition in the master system database in Windows Azure SQL Database.
Based on the error message, there is timeout error when connect to SQL Database. Did you deploy a large database? When move large data to Azure SQL Database, it is recommended to use SQL Server Integration Services (SSIS) and BCP utility.
Or you can try to create a client application with the Data-Tier Application Framework (DACFx) client tool to import database and handle connection loss it by re-establish the connection.
Reference: http://sqldacexamples.codeplex.com/
Regards,
Fanny Liu
If you have any feedback on our support, please click here.
Fanny Liu
TechNet Community Support

Database transactions not opening

Hi,
I am trying to open the transaction codes like db02, db03 etc..None of the database related transaction seems to be opening. It times out..Please advise.

Hello,
Do you get a database timeout (-913, rc00c9008e) or work process timeout (rdisp/max_wprun_time exceeded) ?
In SM50 or tx DB2 -Thread Activity you can identify the hanging statement. If it's a DB timeout Thread Activity shows the blocker of the resource as well (DB Monitor must be active, dependent on th release RFCOSCOL or SAPCL).
Regards,
Thomas

SSRS 2012 report integrated with SharePoint 2013 issue :Report refreshing after some idle time

we have SSRS 2012 report integrated with SharePoint 2013 , when we click on any toggle item after some idle time of 60 secs and try again to expand
another toggle item then complete report is getting refreshed and if we are in child report it is redirecting to parent report. . we didn’t set any refreshing property at report level. I hope there will be some idle time setting at sharepoint site
level.
what we observed.
1. there is no problem when we expand toggle items without any idle time.
2. when we open the report and expand few toggles and keep idle for 60 seconds and try
again to expand another toggle item then complete report is getting refreshed (all toggle items are collapsing).
3. If you keep idle for 60 minutes and if you didn’t do any action like expanding toggle
items it is not refreshing.
why it is happening and how to stop that complete refresh.
Surendra Thota

Hi Surendra,
I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
Please reference to the setting below to don't limit the timeout values if you got the report reloading:
Point to a report in the library.
Click the down arrow, and select Manage processing options.
In Processing Time-out, select Do not time out report processing or
Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
If you got the session timeout that refresh the page, please reference to the setting in below article:
http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
Details information in the article below about the timeout setting for your reference:
Set Processing Options (Reporting Services in SharePoint Integrated Mode)
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
If you have any feedback on our support, please click
here.
Vicky Liu
TechNet Community Support

Error while running SSRS 2012 report integrated with SharePoint 2013

Hi,
Our reporting services environment has SSRS 2012 integrated with SharePoint 2013. The SharePoint 2013 farm has 2 web front ends, 1 app server and a separate server for reporting services i.e SSRS 2012 .
We have created a https web application in SharePoint 2013 and all the SSRS 2012 reports are deployed into a "Report Library" residing in its root site collection.
The simple reports are running well. But there is a report where we have 3 multi-value parameters. On running this report in IE or Chrome, we get the error "Sys.WebForms.PageRequestManagerParserErrorException: The message received from the
server could not be parsed. Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled. Details: Error parsing near ' <!DOCTYPE html PUB'."
Some of the forums suggested to add the below entry in the web config of the SharePoint web app where the SSRS reports are deployed. We did that too, still the error is appearing. Please can anyone help .
<appSettings>
<add key="aspnet:MaxHttpCollectionKeys" value="100000" />
</appSettings>
Thanks

Hi Surendra,
I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
Please reference to the setting below to don't limit the timeout values if you got the report reloading:
Point to a report in the library.
Click the down arrow, and select Manage processing options.
In Processing Time-out, select Do not time out report processing or
Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
If you got the session timeout that refresh the page, please reference to the setting in below article:
http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
Details information in the article below about the timeout setting for your reference:
Set Processing Options (Reporting Services in SharePoint Integrated Mode)
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
If you have any feedback on our support, please click
here.
Vicky Liu
TechNet Community Support

Sqlpackage.exe Azure export error started few days ago

I was using this for a couple of months and suddenly since few days, I can't do it anymore
sqlpackage.exe /a:Export /ssn:xxxxxxx.database.windows.net /sdn:"xxx" /su:"xxx" /sp:"xxxxxxxxxxxxxx" /tf:"xxxxxx.bacpac"
Connecting to database 'xxxxx' on server 'xxxxxxx.database.windows.net'.
Extracting schema
Extracting schema from database
*** Error exporting database:Could not extract package from specified database. Unable to reconnect to database: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. Timeout
expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The wait operation timed out

Alex,
Thanks for contacting Forum support. In the above response by Mekh, he has suggested to open a support ticket for a specific reason
1. SQLPackage.exe doesn't have it's own logging.
2. However if you open a support ticket, we will be able to sql database gateway logs and SQL performance logs which
could have an impact on the SQLPackage.exe.
This post might seem repetitive but it's because of the fact that, the error message is "Could not extract package from specified database. Unable to reconnect to database: Timeout expired." This could mean many things which Mekh has
been discussing with you throughout the post.
One quick question here:
1. What is the frequency of this failing using SQLPackage.exe? (If I remember correctly, this tool is working fine with many other databases. have you tried and found out what is the outstanding change of this DB when compared to other DBs?)
2. When the SQLPackage.exe failed, how was the database performance? Was it over-loaded?
3. Was there any outages at that time? (http://www.windowsazure.com/en-us/support/service-dashboard/)
4. Sometimes, the Dashboard doesn't list all the outages if the impact is not huge in which cases, opening a support ticket helps. The support team contacts the Operations team (who manage the data-center machines) and if required, they involve the Product
Group developers in extreme situations.
5. This is a repetition; the SQLPackage.exe import/export of bacpac/dacpac doesn't have a 'Operation ID'. That means, we cannot trace the failure to check why there was a Timeout/connection issue/performance issue/queue length issue etc.
Again, SQLPackage.exe is not the only tool out there. We strongly recommend you to use tools like Export, Automated exports etc.
With the new SQL Azure DB announcements, you actually don't even need to make a copy of the database using SQLPackage.exe. You can use the Geo-restore/Deleted databases/Restore feature in case of disasters (/Oops delete). For a new service tier database
(Basic/Standard/Premium), we internally maintain backups and in case you need to restore the database, you can use the 'Restore' functionality to restore the database to a point 7 days (Basic tier), 15 days (Standard) and up to 35 days (Premium tier). This
very feature itself solves your very problem of performing an export using SQLPackage.exe. (http://azure.microsoft.com/blog/2014/09/13/azure-sql-database-geo-restore/)
Said that, if you open a support incident, the team will be able to talk to you over the phone and spend good amount of time, have a screen-sharing session, having 1:1 follow-ups, escalation routes etc.
I hope this reply helps you and I hope you will be able to make better business decisions with tools such as SQLPackage.exe itself.
-Karthik (KKB)

0x80230729 (The extension could not be loaded.)

Hi,
I've been working on this most of the day without any luck. I'm wondering if anyone has seen something like this.
PCNS can successfully deliver the password change to an AD target, so PCNS should be OK.
The failure occurs when we add the Oracle EBS Web Service management agent to the password sync targets.
The error message indicates that the Microsoft.IdentityManagement.WebService.MA.dll cannot be loaded due to an incorrect .NET framework version.
An unexpected error has occurred during a password set operation.
"BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(322): 0x80230729 (The extension could not be loaded.)
ERR_: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(804): Please verify that the password extension dll can be located in the Extensions directory.
If the extension is present, confirm that the version of the .NET framework that can run the extension is installed on the server and that a supportedRuntimes entry in the configuration files specifies that version. The synchronization engine will not be able
to load an extension that is built with a newer version of the .NET framework than the version of the .NET runtime it is hosting.BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\core\passwordext.cpp(806): 0x80230729 (The extension could not be loaded.)
BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2821): 0x80230729 (The extension could not be loaded.)
BAIL: MMS(5080): d:\bt\9394412\private\source\miis\ma\extensible\export.cpp(2866): 0x80230729 (The extension could not be loaded.)
BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\exportpassword.cpp(474): 0x80230729 (The extension could not be loaded.)
BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(7961): 0x80230729 (The extension could not be loaded.)
BAIL: MMS(5080): d:\bt\9394412\private\source\miis\server\server\ma.cpp(8410): 0x80230729 (The extension could not be loaded.)
Forefront Identity Manager 4.1.2273.0"
I ran an Environment.Version command and it returns that we are using 4.0.30319.296.
In the dllhost.exe.config file, we have the settings:
<?xml version="1.0" encoding="UTF-16"?>
<configuration>
<configSections>
<section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
</configSections>

<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319"></supportedRuntime>
<supportedRuntime version="v2.0.50727"></supportedRuntime>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
<bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
<bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
So, I think it looks like it should be trying to run the dll under the 4.0.30319 framework. The documentation says that framework is required and we are running it.
The dll is in the Extensions folder.
Has anyone seen this before or something like it? Any ideas on where else I could check?
Thanks,
Sami

Thank you for your reply. I've tried running in and out of proc with the same error showing up.
I tried a few different modifications to the miiserver.exe.config (as well as Mmsscrpt.exe.config and the Dllhost.exe.config files). I tried changing 4.0.30319 to 4.0 as per this article:
http://msdn.microsoft.com/en-us/library/w4atty68.aspx
Even though we are only on FIM R2 (not on SP1), I tried a variation on the config file changes recommended here:
http://support.microsoft.com/kb/2772429 but I referenced the newVersion as 4.0.1.0.
Still no luck.
Here's the miiserver.exe.config file. Maybe you'll see something glaringly wrong? Thank you for your help!
<?xml version="1.0" encoding="UTF-16"?>
<configuration>
<configSections>
    <section name="resourceManagementClient" type="Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClientSection, Microsoft.ResourceManagement"/>
    <section name="resourceManagementService" type="Microsoft.ResourceManagement.WebServices.ResourceManagementServiceSection, Microsoft.ResourceManagement.Service"/>
    <section name="resourceSynchronizationClient" type="MIIS.ManagementAgent.ResourceSynchronizationClientSection, mmsmafim"/>
</configSections>

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319"></supportedRuntime>
    <supportedRuntime version="v2.0.50727"></supportedRuntime>
</startup>

<resourceSynchronizationClient/>

    <system.diagnostics>
        <sources>
            <source name="ForefrontIdentityManager.ManagementAgent" switchValue="Warning">
                <listeners>
                    <add initializeData="ForefrontIdentityManager.ManagementAgent" type="System.Diagnostics.EventLogTraceListener, System, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089"
                         name="MAExceptionEventLogListener" traceOutputOptions="LogicalOperationStack, DateTime, Timestamp, Callstack">
                    <filter type="" />
                    </add>
                </listeners>
            </source>
            <source name="ForefrontIdentityManager.ManagementAgent.EventTracingForWindowsTraceSource" switchValue="Verbose">
                <listeners>
                    <add name="MAEventTracingForWindowsListener"
                         type="System.Diagnostics.Eventing.EventProviderTraceListener, System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"
                         initializeData="{C4D0C1D4-909D-481b-B011-10E682A6009C}" />
                </listeners>
            </source>
        </sources>
    </system.diagnostics>
    
    
    

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0.30319"></supportedRuntime>
    <supportedRuntime version="v2.0.50727"></supportedRuntime>
</startup>
<runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Microsoft.MetadirectoryServicesEx" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="3.3.0.0" newVersion="4.0.1.0" />
        <bindingRedirect oldVersion="4.0.0.0" newVersion="4.0.1.0" />
      </dependentAssembly>
    </assemblyBinding>
</runtime>
</configuration>

How to synchronize between DHCP binding table and DHCP snooping table ?

I clear DHCP snooping table with command "clear ip dhcp snooping binding " , and PC can't communicate with other any more. So how to synchronize between DHCP binding table and DHCP snooping table ?
dhcp-test#sh ip dhcp bind
IP address Client-ID/ Lease expiration Type
Hardware address
99.1.65.32 0100.1125.353c.25 Mar 02 1993 01:05 AM Automatic
99.1.65.33 0100.1438.059f.85 Mar 02 1993 12:01 AM Automatic
dhcp-test#sh ip dhcp snooping binding
MacAddress IpAddress Lease(sec) Type VLAN Interface
Total number of bindings: 0
thanks!

ip dhcp snooping binding mac-address vlan vlan-id ip-address interface interface-id expiry seconds
Add binding entries to the DHCP snooping binding database. The vlan-id range is from 1 to 4904. The seconds range is from 1 to 4294967295.
Enter the above command for each entry that you add
To delete the database agent or binding file, use the no ip dhcp snooping database interface configuration command. To reset the timeout or delay values, use the ip dhcp snooping database timeout seconds or the ip dhcp snooping database write-delay seconds global configuration command.To renew the database, use the renew ip dhcp snooping database privileged EXEC command.

Long duration jdbc connection

Am connection through a thin client to a DB. The transaction runs for 3.5 hours, when i call commit and close the connection no exceptions are thrown. But when i look into the DB, no records are inserted, it appears the Tx did not commit. Autocommit is false,
And yes Verified the database, schema and tables name to ensure was looking at the correct place.
Same program when run for 30 minutes on a smaller input set, works fine, all inserts take place.
Has anybody had a very long Tx >4 hour ,and any thing special done for it.
Thanks
Tapan
Edited by: tapan_mokha on Feb 12, 2009 7:37 AM

or you may have ended up with an automatic rollback after some internal database timeout.
That way your commit would have committed exactly nothing, and (having been started in an automatically created new transaction) wouldn't yield an error.
It's a very weird transaction that requires that much time to run and can't have internediate commits (which would refresh the transaction, avoiding such timeouts).

Database timeout

Similar Messages

Maybe you are looking for